[RESULT][VOTE] Release Apache Cassandra 5.0-beta1 (take2)

> 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. > The vote passes with five +1s (three binding).

Re: [VOTE] Release Apache Cassandra 5.0-beta1 (take2)

+1 Le mar. 5 déc. 2023 à 12:23, Maxim Muzafarov a écrit : > +1 (nb) > > run locally, executed some queries over vts > > On Mon, 4 Dec 2023 at 15:15, Brandon Williams wrote: > > > > +1 > > > > Kind Regards, > > Brandon > > > > On Fri, Dec 1, 2023 at 7:32 AM Mick Semb Wever wrote: > > > > > > >

Re: [VOTE] Release Apache Cassandra 5.0-beta1 (take2)

+1 (nb) run locally, executed some queries over vts On Mon, 4 Dec 2023 at 15:15, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > > On Fri, Dec 1, 2023 at 7:32 AM Mick Semb Wever wrote: > > > > > > Proposing the test build of Cassandra 5.0-beta1 for release. > > > > sha1:

Re: [VOTE] Release Apache Cassandra 5.0-beta1 (take2)

+1 Kind Regards, Brandon On Fri, Dec 1, 2023 at 7:32 AM Mick Semb Wever wrote: > > > Proposing the test build of Cassandra 5.0-beta1 for release. > > sha1: 87fd1fa88a0c859cc32d9f569ad09ad0b345e465 > Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative > Maven Artifacts: >

Re: [VOTE] Release Apache Cassandra 5.0-beta1 (take2)

> 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 are correct - source

Re: [VOTE] Release Apache Cassandra 5.0-beta1 (take2)

+1 (nb) > On Dec 1, 2023, at 7:32 AM, Mick Semb Wever wrote: > >  > > Proposing the test build of Cassandra 5.0-beta1 for release. > > sha1: 87fd1fa88a0c859cc32d9f569ad09ad0b345e465 > Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative > Maven Artifacts: >

[VOTE] Release Apache Cassandra 5.0-beta1 (take2)

Proposing the test build of Cassandra 5.0-beta1 for release. sha1: 87fd1fa88a0c859cc32d9f569ad09ad0b345e465 Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative Maven Artifacts:

[RESULT][VOTE] Release Apache Cassandra 5.0-beta1

> > 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. > With vetoes this vote does not pass. 19011 has been committed, I

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I am supporting releasing to hit the date, At this point it's semantics... Thanks, German From: Maxim Muzafarov Sent: Thursday, November 30, 2023 3:12 AM To: dev@cassandra.apache.org Subject: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-beta1 I'm gonna

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I'm gonna take a moment to outline the question. Here we have a point in time where a time-driven release process clashes with the alpha/beta release naming convention: we want to have a beta ready _before_ the Summit. Here's the Cassandra release lifecycle document [1] that I found (still under

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> > If we end up not releasing a final 5.0 artifact by a Cassandra Summit it > will signal to the community that we’re prioritizing stability and it could > be a good opportunity to get people to test the beta or RC before we stamp > it as production ready. > I agree with Paulo's comment czw.,

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> if any contributor has an opinion which is not technically refuted it will usually be backed by a PMC via a binding -1 clarifying a bit my personal view: if any contributor has an opinion against a proposal (in this case this release proposal) that is not refuted it will usually be backed by a

Re: [VOTE] Release Apache Cassandra 5.0-beta1

To me, the goal of a beta is to find unknown bugs. If no new bugs are found during a beta release, then it can be automatically promoted to RC via re-tagging. Likewise, if no new bugs are found during a RC after X time, then it can be promoted to final. If we end up not releasing a final 5.0

Re: [VOTE] Release Apache Cassandra 5.0-beta1

On Thu, Nov 30, 2023 at 3:28 AM Aleksey Yeshchenko wrote: > -1 on cutting a beta1 in this state. An alpha2 would be acceptable now, > but I’m not sure there is significant value to be had from it. Merge the > fixes for outstanding issues listed above, then cut beta1. > Agree with Aleksey. -1

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> Even though my opinion doesn't really count here, I do feel compelled to > mention that: > Aaron (and anybody who takes the time to follow this list, really), your opinion matters, that's why we discuss it here.

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> So in the context of this thread, if I want to try out SAI for example, I don't care as much about consistency edge cases around coordinators or replicas or read repair. That would apply to 19018, not 19011, which is a critical functionality issue. On Wed, Nov 29, 2023 at 12:49 PM Jeremy Hanna

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I want to just follow up with functional versus production-worthy. If I'm a user interested in C* 5 and want to try it out as betas come out, I'm looking more for something functional and not perfect. So in the context of this thread, if I want to try out SAI for example, I don't care as much

Re: [VOTE] Release Apache Cassandra 5.0-beta1

Even though my opinion doesn't really count here, I do feel compelled to mention that: - No one expects a "beta" release to be perfect, but it does signal that it is "close" to being ready. - An "alpha" release is in fact a LOT scarier than a "beta" release. >From a user perspective, if I was

Re: [VOTE] Release Apache Cassandra 5.0-beta1

-1 on cutting a beta1 in this state. An alpha2 would be acceptable now, but I’m not sure there is significant value to be had from it. Merge the fixes for outstanding issues listed above, then cut beta1. With TCM and Accord pushed into 5.1, SAI is the headliner user-visible feature. It is what

Re: [VOTE] Release Apache Cassandra 5.0-beta1

So then cutting an alpha2 is possible. > Possible, but still leaves alpha1 as our mitigation plan and alpha2 as our best plan. Doesn't seem worth it IMHO.

Re: [VOTE] Release Apache Cassandra 5.0-beta1

So then cutting an alpha2 is possible. Kind Regards, Brandon On Tue, Nov 28, 2023 at 2:59 PM Mick Semb Wever wrote: > > > You can't change bits in a signed and checksummed artefact. You have to cut > from scratch. > > On Tue, 28 Nov 2023 at 20:28, Brandon Williams wrote: >> >> I think the

Re: [VOTE] Release Apache Cassandra 5.0-beta1

You can't change bits in a signed and checksummed artefact. You have to cut from scratch. On Tue, 28 Nov 2023 at 20:28, Brandon Williams wrote: > I think the last time I looked into it there was nothing in the > scripts that forced anything, but if that's not true I think we should > be fixing

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I think the last time I looked into it there was nothing in the scripts that forced anything, but if that's not true I think we should be fixing that, not having it drive our release decisions. Kind Regards, Brandon On Tue, Nov 28, 2023 at 12:54 PM Mick Semb Wever wrote: > > > > On Tue, 28 Nov

Re: [VOTE] Release Apache Cassandra 5.0-beta1

“The QA label is part of our version number and that's baked in.” How can we have beta 2, but there is no way for alpha 2? On Tue, 28 Nov 2023 at 13:55, Mick Semb Wever wrote: > > > On Tue, 28 Nov 2023 at 19:27, J. D. Jordan > wrote: > >> That said. This is clearly better than and with many

Re: [VOTE] Release Apache Cassandra 5.0-beta1

On Tue, 28 Nov 2023 at 19:27, J. D. Jordan wrote: > That said. This is clearly better than and with many fixes from the alpha. > Would people be more comfortable if this cut was released as another alpha > and we do beta1 once the known fixes land? > There is no way with our release process to

Re: [VOTE] Release Apache Cassandra 5.0-beta1

If the consensus is that meaningful community testing will occur in the week between "beta1 but SAI is broken, friends" and "ok, beta2, it's fixed now, go for it"...then go for it. On Tue, Nov 28, 2023 at 12:40 PM Patrick McFadin wrote: > JD, that wasn't my point. It feels like we are treating

Re: [VOTE] Release Apache Cassandra 5.0-beta1

-0 to cutting a beta we know has a very obvious correctness flaw with a fix already understood On Tue, Nov 28, 2023 at 10:40 AM Patrick McFadin wrote: > JD, that wasn't my point. It feels like we are treating a beta like an RC, > which it isn't. Ship Beta 1 now and Beta 2 later. We need

Re: [VOTE] Release Apache Cassandra 5.0-beta1

JD, that wasn't my point. It feels like we are treating a beta like an RC, which it isn't. Ship Beta 1 now and Beta 2 later. We need people looking today because they will find new bugs and the signal is lost on alpha. It's too yolo for most people. On Tue, Nov 28, 2023 at 10:36 AM Benjamin Lerer

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I'm fine w/ alpha2 now and beta1 once we resolve 19011. On Tue, Nov 28, 2023 at 12:36 PM Benjamin Lerer wrote: > -1 based on the problems raised by Caleb. > > I would be fine with releasing that version as an alpha as Jeremiah > proposed. > > As of this time, I'm also not aware of a user of the

Re: [VOTE] Release Apache Cassandra 5.0-beta1

-1 based on the problems raised by Caleb. I would be fine with releasing that version as an alpha as Jeremiah proposed. As of this time, I'm also not aware of a user of the project operating a > build from the 5.0 branch at substantial scale to suss out the operational > side of what can be

Re: [VOTE] Release Apache Cassandra 5.0-beta1

That said. This is clearly better than and with many fixes from the alpha. Would people be more comfortable if this cut was released as another alpha and we do beta1 once the known fixes land?On Nov 28, 2023, at 12:21 PM, J. D. Jordan wrote:-0 (NB) on this cut. Given the concerns expressed so

Re: [VOTE] Release Apache Cassandra 5.0-beta1

-0 (NB) on this cut. Given the concerns expressed so far in the thread I would think we should re-cut beta1 at the end of the week.On Nov 28, 2023, at 12:06 PM, Patrick McFadin wrote:I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect especially if there are declared known issues.

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect especially if there are declared known issues. We need people outside of this tight group using it and finding issues. I know how this rolls. Very few people touch a Alpha release. Beta is when the engine starts and we need to get

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> > 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 are correct - source

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> > Compared to the rigor of our previous major release, this feels rushed and > timeline-driven rather than anchored in values of quality and data > integrity. > Yes, it is (unfortunately) time-driven. But rather than say rushed I would say incremental. At the Summit, whatever release we end

Re: [VOTE] Release Apache Cassandra 5.0-beta1

Agreed with Brandon, yes. I'm at a "-0 (nb)" on a beta release at this point. We're clearly finding (and resolving) lots of significant and in some case serious issues - ones that violate fundamental properties of the database. I'm very glad that we're finding and fixing these, but they feel

Re: [VOTE] Release Apache Cassandra 5.0-beta1

If we are going to commit to beta2 before the summit because "putting a beta w/ SAI in this state into users’ hands at summit would be very, very bad" I don't see why we need to have a subpar beta1 at all? Kind Regards, Brandon On Tue, Nov 28, 2023 at 11:16 AM Mick Semb Wever wrote: > > > > On

Re: [VOTE] Release Apache Cassandra 5.0-beta1

On Tue, 28 Nov 2023 at 18:06, Caleb Rackliffe wrote: > Just to update this thread, Mike has identified the root cause of 19011 > and in the process uncovered 2 additional very closely related issues. > (Fantastic job fuzzing there!) Fixes for all three issues are in hand, and > he continues to

Re: [VOTE] Release Apache Cassandra 5.0-beta1

Just to update this thread, Mike has identified the root cause of 19011 and in the process uncovered 2 additional very closely related issues. (Fantastic job fuzzing there!) Fixes for all three issues are in hand, and he continues to test.After some conversation w/ Mick, Alex, and Mike, I feel

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> Furthermore, we don't even know if it's still an issue after 19034 was committed. It's a difficult one to reproduce because we don't have access to the harry script that generated the error in the first place. I am investigating it but without the original reproduction it may take some time.

Re: [VOTE] Release Apache Cassandra 5.0-beta1

On Mon, 27 Nov 2023 at 16:28, Brandon Williams wrote: > On Mon, Nov 27, 2023 at 9:25 AM Mick Semb Wever wrote: > > > > It was agreed to move them to 5.0-rc > > Where? > Typo, "it" not "them". I'm only talking about 19011. The others were already 5.0-rc, or infact forward from 5.0.x. Here:

Re: [VOTE] Release Apache Cassandra 5.0-beta1

On Mon, Nov 27, 2023 at 9:25 AM Mick Semb Wever wrote: > > It was agreed to move them to 5.0-rc Where?

Re: [VOTE] Release Apache Cassandra 5.0-beta1

It was agreed to move them to 5.0-rc, and to complete any further triage/investigation of any tickets deemed potentially critical early this week before the vote window closes. SAI is a new feature, not enabled by default, so IMHO this is an acceptable call. And some of those tickets look like

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I propose to consider including https://issues.apache.org/jira/browse/CASSANDRA-18464 (started a separate thread) pon., 27 lis 2023 o 13:06 Benjamin Lerer napisał(a): > Looking at the board it is unclear to me why CASSANDRA-19011 > ,

Re: [VOTE] Release Apache Cassandra 5.0-beta1

Looking at the board it is unclear to me why CASSANDRA-19011 , CASSANDRA-19018 , CASSANDRA-18796 and CASSANDRA-18940

[VOTE] Release Apache Cassandra 5.0-beta1

Proposing the test build of Cassandra 5.0-beta1 for release. sha1: e0c0c31c7f6db1e3ddb80cef842b820fc27fd0eb Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative Maven Artifacts: