We hashed this out a bit in slack and I think the current rough consensus (please speak up if you don't agree) is that we update our release guidelines [1] to allow API changes between alpha and beta as the common artifact is useful for testing and we will probably end up finding API breakage while testing that must be fixed. Benedict helped out by creating 4.0-alpha [2] and 4.0-beta [3] fix versions so we can track what tickets are (roughly) blocking the next alpha/beta release. If you feel that something you're working on should block the alpha or the beta please help out and tag it with the proper fix version. The idea is that we know which outstanding tickets exist and are impacting the next alpha/beta, even if we ignore it and cut anyways at least we can separate "this has to happen before beta" from "this has to happen before release candidates".
I think the next decision is should we just cut 4.0-alpha1 now given that Michael has some cycles regardless of the known issues and start using the new fix versions for the 4.0-alpha2 release? I personally feel we should cut 4.0-alpha1 with every imaginable "expect this release to break" disclaimer and start working towards 4.0-alpha2. [1] https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%204.0-alpha [3] https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%204.0-beta What do people think? -Joey On Wed, Aug 28, 2019 at 10:58 AM Michael Shuler <mich...@pbandjelly.org> wrote: > > Thanks for the reminder :) I have a few days of availability to prep a > 4.0 alpha release. It's an alpha, so I don't have a problem with known > issues needing work. > > I will have an internet-less period of time starting roughly Tuesday 9/3 > through about Friday 9/13. I might get lucky and have a little network > access in the middle of that time, but I'm not counting on it. > > -- > Michael > > On 8/28/19 10:51 AM, Jon Haddad wrote: > > Hey folks, > > > > I think it's time we cut a 4.0 alpha release. Before I put up a vote > > thread, is there a reason not to have a 4.0 alpha before ApacheCon / > > Cassandra Summit? > > > > There's a handful of small issues that I should be done for 4.0 (client > > list in virtual tables, dynamic snitch improvements, fixing token counts), > > I'm not trying to suggest we don't include them, but they're small enough I > > think it's OK to merge them in following the first alpha. > > > > Jon > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
