This is completed now, thanks to all those who helped! The merge order for release blockers is:
cassandra-3.0->cassandra-3.11->cassandra-4.0.0->cassandra-4.0->trunk For anything non-critical, you skip 4.0.0, but explicitly: cassandra-3.0->cassandra-3.11->cassandra-4.0->trunk On Thu, Jun 3, 2021 at 11:32 AM Brandon Williams <dri...@gmail.com> wrote: > > I've created https://issues.apache.org/jira/browse/CASSANDRA-16709 for > the 4.0.0 branch > > On Thu, Jun 3, 2021 at 11:06 AM Ekaterina Dimitrova > <e.dimitr...@gmail.com> wrote: > > > > +1, thank you Brandon > > > > @Jeff - there is the Jira board Cassandra 4.0GAScope > > It might need some revision though. Any help with flaky tests is also > > appreciated if anyone has cycles. Thank you all, let’s do it :-) > > > > On Thu, 3 Jun 2021 at 11:45, Jeff Jirsa <jji...@gmail.com> wrote: > > > > > Given we're past the RC1, I think it's time. > > > > > > Also, probably a silly question, but where's the list of issues reported > > > in > > > the release candidate that need to be fixed before the GA? > > > > > > > > > On Thu, Jun 3, 2021 at 8:36 AM Brandon Williams <dri...@gmail.com> wrote: > > > > > > > Hello, > > > > > > > > In order to more safely expedite 4.0's first release, I would like to > > > > propose minimizing the surface area for regressions by creating a 4.0.0 > > > > branch, as we have done in the past for initial releases. Only critical > > > > bugfixes would go in this branch, essentially removing it from the merge > > > > order otherwise. This should allow everyone to scratch the itches they > > > > choose without introducing any unnecessary risk to the impending 4.0.0 > > > > release. Thoughts? > > > > > > > > Kind Regards, > > > > Brandon > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
