The thing is, good intentions are cheap. And they get cheaper the further out in the future the point of action gets.
Realistically, the main difference between June and September is we ship three months later. More, if we manage to land large, destabilizing patches in the meantime. I’m very skeptical it will actually result in additional testing. In my experience, people start testing once you actually have an alpha or beta released. And even then they prefer to wait for a dot zero. We only have about nine years of project history showing this, though. I’m sure this time will be different. On Thu, Apr 12, 2018 at 3:59 PM Ben Bromhead <b...@instaclustr.com> wrote: > While I would prefer earlier, if Sept 1 gets better buy-in and we can have > broader commitment to testing. I'm super happy with that. As Nate said, > having a solid line to work towards is going to help massively. > > On Thu, Apr 12, 2018 at 4:07 PM Nate McCall <zznat...@gmail.com> wrote: > > > > If we push it to Sept 1 freeze, I'll personally spend a lot of time > > testing. > > > > > > What can I do to help convince the Jun1 folks that Sept1 is acceptable? > > > > I can come around to that. At this point, I really just want us to > > have a date we can start talking to/planning around. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > -- > Ben Bromhead > CTO | Instaclustr <https://www.instaclustr.com/> > +1 650 284 9692 > Reliability at Scale > Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer > -- Jonathan Ellis co-founder, http://www.datastax.com @spyced
