https://lists.apache.org/thread.html/5ee66f3986bf8308912c216bd1b5f9aea35443626db9f92cdca4d7b9%40%3Cdev.cassandra.apache.org%3E
"*From: *sankalp kohli <k...@gmail.com> *To: *dev <d...@cassandra.apache.org> *Subject: *Re: [VOTE] Branching Change for 4.0 Freeze *Date: *2018/07/11 21:50:08 *List: *dev@cassandra.apache.org <https://lists.apache.org/list.html?dev@cassandra.apache.org> We will be in this state till beta is reached." The release lifecycle doc says: "*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.*" This could be read as "we won't branch until we hit GA" or "we will make sure we definitely branch at GA so disruptive features don't go into it", the latter of which is what we've done in all prior releases. I'm curious if there was any point in that discussion where the intention was made explicit if anyone has a link. On Thu, Sep 24, 2020 at 11:53 AM, Benedict Elliott Smith < bened...@apache.org> wrote: > I'm not sure what you are referring to here, that vote said nothing about > branching at beta. > > The most recent vote on the topic anyway was for the Release Lifecycle > process, which stipulates branching at GA. > > https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle > > We can vote to modify this document, or to make an exception, but I am > aware of no other vote stipulating anything about the point at which we > branch. > > On 24/09/2020, 16:49, "Jake Luciani" <jak...@gmail.com> wrote: > > Today the community still has in force an explicit vote prohibiting thee > > merge of this work. > > You referred to an explicit vote here. I assume that was the one you were > referring to? Yes, the community should decide. > Call a vote if you think the community thinks we should continue the > freeze vs continuing to rely on beliefs about the community. > > I'm simply pointing out the branching of 4.0 post beta was the plan of > last record. > > Jake > > On Thu, Sep 24, 2020 at 11:44 AM Benedict Elliott Smith <benedict@apache. > org> wrote: > > The community does everything through discussion and consensus. Does that > include branching, or not? > > If there is no consensus, a vote is held. Whether or not you consider the > vote from 2018 still valid, you still need to seek the consent of the > community for your action today. Or is that not sacrosanct anymore? > > On 24/09/2020, 16:22, "Jake Luciani" <jak...@gmail.com> wrote: > > I'm sorry I see no issue with branching 4.0 as it was the thing we voted > on > back in 2018. If you wish to extend the freeze you should call a new vote. > > On Thu, Sep 24, 2020 at 11:15 AM Benedict Elliott Smith < benedict@apache. > org> > wrote: > > Nobody has any problem with an external repository being > > maintained. Just > > bear in mind the normal process will need to take place to merge to > > the ASF > > repository, and that there may be feedback and review requests to > > address, > > so merge order and diffs will probably change. > > On 24/09/2020, 16:05, "Brandon Williams" <dri...@gmail.com> wrote: > > On Thu, Sep 24, 2020 at 9:55 AM Benedict Elliott Smith > <bened...@apache.org> wrote: > > You do not have the authority to unilaterally overrule the > > community > > process. This is a serious breach of your responsibilities as a > > member of > > the PMC. > > Feel free to complain that I'm creating branches we intend to > > someday, > > perhaps even in 2020, release. > > I have deleted this branch, and will do so again if you repeat > > this. > > This would create some interesting tickets for INFRA, but I won't waste > their time with you either. Whether either of us has the authority to do > such on ASF infrastructure is irrelevant, since > > that > > is the only thing that can be argued here. The ASL absolutely > > allows > > people to innovate on their own with the code, so let's just > > move the > > bits. > > Those who wish to innovate, > https://github.com/driftx/cassandra/tree/cassandra-5.0 is now > > open for > > business, PRs accepted. This will be maintained to track trunk > > on the > > ASF servers. > > I guess this is the apache way. > > --------------------------------------------------------------------- > > 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 > > -- > http://twitter.com/tjake > > --------------------------------------------------------------------- To > unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional > commands, e-mail: dev-h...@cassandra.apache.org > > -- > http://twitter.com/tjake > > --------------------------------------------------------------------- To > unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional > commands, e-mail: dev-h...@cassandra.apache.org >
