Not really important IMO if we do or do not cut a new branch yet. So let’s hold off?
But as mentioned on Slack, I really like the idea of cutting an alpha now, with clear understanding that the API will still slightly change before the 4.0-GA. There is enough complete work in trunk that will *not* change between now and GA that could benefit from user testing already. > On 30 Aug 2019, at 12:46, Mick Semb Wever <m...@apache.org> wrote: > > >> >> Let's just pull the trigger on it. We know there are a couple of rough >> edges, but that is the point of an alpha. > > > Is the idea to also cut 2.2.15, 3.0.19, and 3.11.5, at the same time as > 4.0-alpha1 ? > > (Michael, have you the cycles for this?) > > regards, > Mick > > --------------------------------------------------------------------- > 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
