> My thinking was talking about when to lift the freeze was moot if we hadn't branched, and the agreed upon release lifecycle is pretty clear that we don't branch until GA. Am I misunderstanding the relationship there?
The proposal of this thread is to branch and lift the freeze before GA. I agree to this proposal but I'm suggesting we close and codify the release cadence discussion from [1] before we lift the freeze, and maybe kick off the roadmap discussion but we probably shouldn't block the unfreeze on this. Looking back at the thread from [1] I saw that while we reached an agreement on the release cadence, we haven't discussed how we plan to ensure the quality of the releases moving forward, so we should also kick off this discussion but also don't need to block branching on this. [1] - http://mail-archives.apache.org/mod_mbox/cassandra-dev/202101.mbox/%3ccabxe4tqrft9yn9tscd0jcs4qxe4vfeezqqtkbcw16d+3rgg...@mail.gmail.com%3e Em qui., 25 de mar. de 2021 às 12:00, Joshua McKenzie <jmcken...@apache.org> escreveu: > > > > be very practical and codify our existing agreements > > discussed on the mentioned threads before lifting the freeze > > Ah. My thinking was talking about when to lift the freeze was moot if we > hadn't branched, and the agreed upon release lifecycle is pretty clear that > we don't branch until GA. Am I misunderstanding the relationship there? > > On Thu, Mar 25, 2021 at 10:56 AM Paulo Motta <pauloricard...@gmail.com> > wrote: > > > > That said, I think freezing feature contribution and not branching > until > > GA like we've newly done with 4.0 is bad for the health of the project > > > > +1. I think the freeze and branching until GA was atypical and unique to > > 4.0 and won't be repeated in the upcoming releases. I agree with > Sumanth's > > proposal on the release doc that branching should not be tied to a > specific > > release phase but decided independently by the community during the > release > > process (as it's being done now). > > > > > I think we should probably discuss the release process separately and > > revise our agreements and process based on learnings from this release. > > > > Just to clarify: I'm not proposing we make a lengthy revision of the > > release process, but be very practical and codify our existing agreements > > discussed on the mentioned threads before lifting the freeze and discuss > > any remaining concerns (just to ensure we will not leave this for later > and > > have clear expectations for the next release cycles). > > > > Em qui., 25 de mar. de 2021 às 11:10, Joshua McKenzie < > > jmcken...@apache.org> > > escreveu: > > > > > The current "Release Lifecycle" wiki doc speaks to when we branch: > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle > > > > > > Specifically under "General Availability (GA)": > > > > > > - A new branch is created for the release with the new major > version, > > > limiting any new feature addition to the new release branch, with > new > > > feature development will continue to happen only on trunk. > > > > > > > > > That said, I think freezing feature contribution and not branching > until > > GA > > > like we've newly done with 4.0 is bad for the health of the project. > > Also, > > > I don't think the project can survive another release cycle as long and > > as > > > exclusionary as the 4.0 release has been (judging by declining > > contribution > > > volume, declining external ticket creation and interactions, and > > db-engine > > > indicators of popularity declining), so I think we should probably > > discuss > > > the release process separately and revise our agreements and process > > based > > > on learnings from this release. > > > > > > Just my .02 though as I'm no longer actively involved. > > > > > > On Thu, Mar 25, 2021 at 9:15 AM Paulo Motta <pauloricard...@gmail.com> > > > wrote: > > > > > > > I agree we should start considering branching 4.0 and unfreezing > soon, > > > but > > > > before I think we should: > > > > - Close the loop on the agreed points of the "releases after 4.0" [1] > > and > > > > "project roadmap" [2] threads and document the new release guidelines > > > > post-4.0 so we have a good starting point. > > > > - Revisit the previous discussions on unfreezing 4.0 and address any > > > > remaining concerns that may still be open. > > > > > > > > Looking forward to this exciting milestone! > > > > > > > > [1] - > > > > > > > > > > > > > > http://mail-archives.apache.org/mod_mbox/cassandra-dev/202101.mbox/%3ccabxe4tqrft9yn9tscd0jcs4qxe4vfeezqqtkbcw16d+3rgg...@mail.gmail.com%3e > > > > [2] - > > > > > > > > > > > > > > http://mail-archives.apache.org/mod_mbox/cassandra-dev/202103.mbox/%3c050276ba-d9da-40a9-9eb3-c0087b45b...@apache.org%3e > > > > > > > > > > > > Em qui., 25 de mar. de 2021 às 09:34, Ekaterina Dimitrova < > > > > e.dimitr...@gmail.com> escreveu: > > > > > > > > > Hi Benjamin, > > > > > Thanks for bringing it up. I support the idea. > > > > > I saw more activity from new contributors lately, also Google > Summer > > of > > > > > Code is around the corner. Plus I feel it gives a very positive > > signal > > > > > about the state of the project. > > > > > The amount of tickets before GA is really quite low. CI is almost > > > > green, I > > > > > almost haven’t seen a test failure because of product problem but > > > mostly > > > > > tests issues. We are so close, it is very exciting time for this > > > project. > > > > > Best regards, > > > > > Ekaterina > > > > > > > > > > On Thu, 25 Mar 2021 at 8:25, Benjamin Lerer <ble...@apache.org> > > wrote: > > > > > > > > > > > Hi everybody, > > > > > > > > > > > > We are now extremely close to releasing 4.0-RC, the number of > > tickets > > > > > left > > > > > > in the 4.0-GA scope is 20 and only 3 of them are not assigned > yet. > > By > > > > > > consequence, I was wondering if it would make sense to create a > 4.0 > > > > > branch > > > > > > and unfreeze trunk when we release RC. > > > > > > > > > > > > The advantages I see are that it will highly increase the scope > of > > > > > tickets > > > > > > on which newcomers can work on and will allow people to move > > smoothly > > > > to > > > > > > 4.0.X tickets when there are no more available tickets in the 4.0 > > GA > > > > > scope. > > > > > > > > > > > > What do you think? > > > > > > > > > > > > Benjamin > > > > > > > > > > > > > > > > > > > > >
