> > The effort of the cassandra-5.0 branch maintenance: rebasing (git rerere); > is just upon those that wish to take it on
I don't follow. If a bug fix goes into 4.0 do we not need to sync this with 5.0, if so then this would be the 5th branch to keep in-sync, and if the feature freeze is lifted then this branch may diverge making it harder to apply the patch to. Tickets that have been reviewed and are (aside from the feature-freeze) > ready to be committed, can be committed to the `cassandra-5.0` branch Is there such a backlog of tickets that have been reviewed and not going into 4.0.0? What I see are ideas and things punted from review, so it would be good to see what this backlog is and how large. My main fear is reviews of new tickets. A complaint I have heard multiple times from several people is that not enough people are reviewing and reviews take a long time (number of reviewers is small and their backlog keeps growing). If we open up reviews for non 4.0.0 work then my fear is that even less review time will be allocated to 4.0.0 work. - who would be willing to help maintain this cassandra-5.0 branch? I do not have the time so I will not be able to help with 5.0 work. - should it be kept external in a GH fork? Or would you rather have the > branch in our main git repository? To me GH fork is the same as not committed and not reviewed. If a fork would help the community then I am ok with it, but I don't see it as ready to commit. On Thu, Sep 10, 2020 at 12:58 PM Mick Semb Wever <m...@apache.org> wrote: > We know we are turning away more and more contributions and new potential > dev community with our 4.0 feature freeze, and it has been going on for a > while now. > > I would like to suggest we create a cassandra-5.0 branch where we can start > to queue up all reviewed and ready-to-go post-4.0 commits. > > This is not to distract from getting 4.0 out, where our primary focus is, > but as a stop-gap in losing those contributions. The effort of the > cassandra-5.0 branch maintenance: rebasing (git rerere); is just upon those > that wish to take it on, and the branch can be located in whatever GH > fork those > individuals wish to keep it in. Tickets that have been reviewed and are > (aside from the feature-freeze) ready to be committed, can be committed to > the `cassandra-5.0` branch while their tickets remain in "Ready to Commit" > status. The goal of this effort would be, a) we are giving the signal to > contributors to get involved again (even while our primary focus in on > stabilisation and testing efforts), and b) maintaining CI status on the > sequence of commits that are ready to go into trunk post 4.0-rc. > > My questions are… > - who would be willing to help maintain this cassandra-5.0 branch? > - should it be kept external in a GH fork? Or would you rather have the > branch in our main git repository? > > regards, > Mick >
