On Thu, Apr 12, 2018 at 11:21 AM Sankalp Kohli <kohlisank...@gmail.com>

> We can fix test after freezing if there are resources people are willing
> to put. We need to gather support to see who can help with the 3 points I
> have mentioned and when.

Again though, without disagreeing with your points, those don't play into
when we freeze. If we freeze tomorrow, even if it take 3 months to gather
sufficient support for testing, there will still be less to test than if we
push the freeze in 3 months and more things are committed in that
time-frame. And in fact, the sooner we freeze, the sooner the project is
making the statement that people that are willing to contribute to the
project should now do so helping testing rather than continuing working on
their pet ticket. And don't get me wrong, it's an open source project, we
can't force anyone to do anything, so people may continue working on there
pet ticket even after freeze. But we can at least, as a project, make it
clear what kind of contributions are "preferred" at any given time.

> On Apr 12, 2018, at 02:13, Sylvain Lebresne <lebre...@gmail.com> wrote:
> >>
> >> I agree there's little point freezing if we can't even test the system
> >> properly.
> >>
> >
> > I'll mention that I really don't follow the logic of such claim. Why
> can't
> > we
> > fix the testing of the system after freezing? In fact, isn't the whole
> > point of freezing agreeing that it's high time to fix that? Isn't it
> easier
> > to fix tests (and focus on the testing environment if needs be) when
> > things are frozen and code isn't changing from under you?
> >
> > PS: all the questions of this email are rhetorical.
> >
> > --
> > Sylvain
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to