The new release lifecycle guarantees changes these dynamics. Given our commitment to API stability between beta 1 and GA, this has introduced a time where changes being deferred to the next major due to API modification will be unable to be merged unless we branch upon beta.
This warrants another discuss thread I think rather than nesting it here. I'll take that on. On Fri, Jun 26, 2020 at 4:38 AM Mick Semb Wever <m...@apache.org> wrote: > > > > Also, what is the plan for cutting beta branch? I am still learning the > > Apache/C* way so excuse me if I missed something. Looking at the > Lifecycle > > document, I see a point only about GA major version branch. > > My understanding is that we are already in freeze for big changes. When > > would be the right time for creating a beta branch? Something more than > > closing the last beta blockers tickets? > > > > My understanding from the doc is that creating the release branch > `cassandra-4.0` happens with GA. That means we're working on trunk until > GA. Previously C* hasn't had any branches but these release branches, i.e. > no beta or rc branches… (afaik) > > I would have thought it better to branch on RC? if at that point much of > the testing efforts are subsiding, and folk are ready for other things. >
