You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Michael McCandless <lu...@mikemccandless.com> on 2010/05/06 14:20:31 UTC
resurrect back-compat tests on trunk?
I know we removed the back-compat tests (in "backwards" sub-dir), on
trunk, because changes to trunk are not required to be
back-compatible...
But, I think they could still be useful, in that they would tell us
when we did break back-compat, giving us a chance to say "right that's
what I intended" or "woops I didn't mean to do that".
This could also help us keep the migration guide (we need to create it
still :) ) in check, ie, if a commit touches backwards/*, the
migration guide should also be updated.
Thoughts?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: resurrect back-compat tests on trunk?
Posted by Shai Erera <se...@gmail.com>.
Hmm I guess you're right.
Shai
On Thu, May 6, 2010 at 3:48 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> On Thu, May 6, 2010 at 8:39 AM, Shai Erera <se...@gmail.com> wrote:
>
> > We should also develop the backwards test layer for trunk as we go along.
> We
> > cannot do it after trunk is released.
>
> Can't we move the trunk tests to "backwards" upon major release?
>
> Ie the tests we have now on trunk would become 4.0's backwards tests
> once we release 4.0?
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: resurrect back-compat tests on trunk?
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Thu, May 6, 2010 at 8:39 AM, Shai Erera <se...@gmail.com> wrote:
> We should also develop the backwards test layer for trunk as we go along. We
> cannot do it after trunk is released.
Can't we move the trunk tests to "backwards" upon major release?
Ie the tests we have now on trunk would become 4.0's backwards tests
once we release 4.0?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: resurrect back-compat tests on trunk?
Posted by Shai Erera <se...@gmail.com>.
+1
We should also develop the backwards test layer for trunk as we go along. We
cannot do it after trunk is released.
Shai
On Thu, May 6, 2010 at 3:29 PM, Robert Muir <rc...@gmail.com> wrote:
> On Thu, May 6, 2010 at 8:20 AM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
>> I know we removed the back-compat tests (in "backwards" sub-dir), on
>> trunk, because changes to trunk are not required to be
>> back-compatible...
>>
>> But, I think they could still be useful, in that they would tell us
>> when we did break back-compat, giving us a chance to say "right that's
>> what I intended" or "woops I didn't mean to do that".
>>
>> This could also help us keep the migration guide (we need to create it
>> still :) ) in check, ie, if a commit touches backwards/*, the
>> migration guide should also be updated.
>>
>> Thoughts?
>>
>
> +1
>
> --
> Robert Muir
> rcmuir@gmail.com
>
Re: resurrect back-compat tests on trunk?
Posted by Robert Muir <rc...@gmail.com>.
On Thu, May 6, 2010 at 8:20 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> I know we removed the back-compat tests (in "backwards" sub-dir), on
> trunk, because changes to trunk are not required to be
> back-compatible...
>
> But, I think they could still be useful, in that they would tell us
> when we did break back-compat, giving us a chance to say "right that's
> what I intended" or "woops I didn't mean to do that".
>
> This could also help us keep the migration guide (we need to create it
> still :) ) in check, ie, if a commit touches backwards/*, the
> migration guide should also be updated.
>
> Thoughts?
>
+1
--
Robert Muir
rcmuir@gmail.com