> > A hard date for a feature freeze makes sense, a hard date for a release > does not.
Strongly agree. We should also collectively define what "Done" looks like post freeze so we don't end up in bike-shedding hell like we have in the past. On Tue, Apr 3, 2018 at 5:35 PM, Jeff Jirsa <jji...@gmail.com> wrote: > A hard date for a feature freeze makes sense, a hard date for a release > does not. > > -- > Jeff Jirsa > > > > On Apr 3, 2018, at 2:29 PM, Michael Shuler <mich...@pbandjelly.org> > wrote: > > > > On 04/03/2018 03:51 PM, Nate McCall wrote: > >>> My concrete proposal would be to declare a feature freeze for 4.0 in 2 > >>> months, > >>> so say June 1th. That leave some time for finishing features that are > in > >>> progress, but not too much to get derailed. And let's be strict on that > >>> freeze. > >> > >> I quite like this suggestion. Thanks, Sylvain. > > > > Should we s/TBD/somedate/ on the downloads page and get the word out? > > > > Apache Cassandra 3.0 is supported until 6 months after 4.0 release (date > > TBD). > > Apache Cassandra 2.2 is supported until 4.0 release (date TBD). > > Apache Cassandra 2.1 is supported until 4.0 release (date TBD) with > > critical fixes only. > > > > -- > > Kind regards, > > Michael > > > > --------------------------------------------------------------------- > > 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 > >
