Hi,
I would update the asc file (and KEYS file if needed) so that if any user tries
to verify the release, it can be verified.
Kind Regards,
Justin
Hi,
Correct as it didn't contain a +1 in it.
Justin
> Given that CASSANDRA-17495 was not released in any GA (just in 5.0-alpha1), I
> think that the option 1) is still viable - we would drop CASSANDRA-17495 and
> we would have CASSANDRA-19556 instead of that which would act as a global
> on/off on all schema modifications however given that we go
+1
On Thu, May 2, 2024 at 11:36 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.5 for release.
>
> sha1: 6b134265620d6b39f9771d92edd29abdfd27de6a
> Git: https://github.com/apache/cassandra/tree/4.1.5-tentative
> Maven Artifacts:
> https://repository.apache.org/content/rep
+1
Kind Regards,
Brandon
On Thu, May 2, 2024 at 10:16 AM Brandon Williams wrote:
>
> Proposing the test build of Cassandra 4.0.13 for release.
>
> sha1: a6fb3b76feb8467d314b116f937322e1989b42e1
> Git: https://github.com/apache/cassandra/tree/4.0.13-tentative
> Maven Artifacts:
> https://reposito
On Wed, 8 May 2024 at 02:33, Justin Mclean wrote:
> Hi,
>
> The Cassandra download page [1] includes signature files, but you also
> need to include a link to the KEYS files to verify these. Relevant ASF
> policy is here [2].
>
> Trying the verify the latest source release, it fails with this err
