lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shai Erera <ser...@gmail.com>
Subject Re: [DISCUSSION] Trunk and Stable release strategy
Date Mon, 24 Jan 2011 18:59:17 GMT
Glad that we reached consensus on this one so quickly :).

Another thing - I think it'd also make sense to stop fixing bugs on 3.0 once
we release 3.1. That way, we can have bug-fix releases for 2.9 and latest
released 3.x. We then have two options about 3.0.4 (not yet released):
1) Release it (as it includes some bug fixes) and say "this will be the last
3.0.x release".
2) Don't release it and say "any bugs found in 3.0 are either fixed in 3.1
or will be fixed in 3.1.x".

I personally don't have any strong feelings about either option, but option
#2 involves much less efforts :).

Shai

On Mon, Jan 24, 2011 at 3:50 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> +1
>
> Mike
>
> On Mon, Jan 24, 2011 at 8:32 AM, Robert Muir <rcmuir@gmail.com> wrote:
> > On Mon, Jan 24, 2011 at 4:07 AM, Shai Erera <serera@gmail.com> wrote:
> >> This will allow us to release 3x as frequent as we want, hold on w/
> trunk as
> >> much as we want, and at some point cut over to 4.0 and think about the
> next
> >> big things we'd like to bring to Lucene.
> >>
> >
> > +1, this way development is simple: we are always working on the next
> > big release in trunk (for incompatible changes), and port compatible
> > changes back to the next minor release.
> > this seems to be working now, so lets stick with what works.
> > when we release 4.0, 3.x goes into bugfix-mode like 2.9 is now, we
> > start working on 5.0 in trunk, and open up branch_4x to backport
> > compatible changes (e.g. for 4.1)
> >
> > also, I think its simpler to users: no confusion such as 4.1 not being
> > able to read 3.4 indexes or similar silliness: to the users the
> > versions are still completely sequential.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

Mime
View raw message