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 > > >