A lot of good points and everyone's input is really appreciated.

So it sounds like we are building consensus towards June 1 for 4.0
branch point/feature freeze and the goal is stability. (No one has
come with a hard NO anyway).

I want to reiterate Sylvain's point that we can do whatever we want in
terms of dropping a new feature 4.1/5.0 (or whatev.) whenever we want.

In thinking about this, what is stopping us from branching 4.0 a lot
sooner? Like now-ish? This will let folks start hacking on trunk with
new stuff, and things we've gotten close on can still go in 4.0
(Virtual tables). I guess I'm asking here if we want to disambiguate
"feature freeze" from "branch point?" I feel like this makes sense.

To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to