I will pull this candidate and re-cut when CASSANDRA-20976 lands. Paulo, 4.1 didn't get cut as the reason for cutting 4.0.19 was CASSANDRA-20848 which already is released in 4.1.10
> On 16 Oct 2025, at 18:17, Štefan Miklošovič <[email protected]> wrote: > > I am also for the re-staging with CASSANDRA-20976 in. It seems its > merge is imminent. > > On Thu, Oct 16, 2025 at 3:59 PM Paulo Motta <[email protected]> wrote: >> >> >> Should we wait for CASSANDRA-20976 to land, since this is a user-facing >> issue in 5.0? >> >> Also, is there any reason why we are releasing 4.0 and 5.0 but not 4.1 ? >> >> On Thu, Oct 16, 2025 at 2:56 AM Mick <[email protected]> wrote: >>> >>> >>> >>>> The vote will be open for 72 hours (longer if needed). Everyone who has >>>> tested the build is invited to vote. Votes by PMC members are considered >>>> binding. A vote passes if there are at least three binding +1s and no -1's. >>> >>> >>> >>> >>> +1 >>> >>> Checked >>> - signing correct >>> - checksums correct >>> - source artefact builds (JDK 11+17) >>> - binary artefact runs (JDK 11+17) >>> - debian package runs (JDK 11+17) >>> - debian repo runs (JDK 11+17) >>> - redhat* package runs (JDK11+17) >>> - redhat* repo runs (JDK 11+17) >>> >>>
