>> >> So long as non-user-visible improvements, including big ones, can still go >> in 4.0 at that stage, I’m all for it. > > > My understanding is that after June 1st the 4.0 branch would be created and > would be bugfix only. It's not really a feature freeze if you allow > improvements after that, which is why they'd instead go to trunk. > > I'm also on the "too soon" train so pushing it back to August or so is > desirable to me. >
For those wanting to delay, are we just dancing around inclusion of some pet features? This is fine, I just think we need to communicate what we are after if so. We can do two things: 1. Lay our cards on the table about what we want included in 4.0 and work to get those in 2. Agree to keep June 1 follow up a lot quicker with a 4.1 I do want to remind everyone though that each new feature is at odds with our stability goals for 4.0. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
