+1 on calling them 3x and trunk. Then as 3.1, 3.2 etc are released, we
create appropriate branches + tags, like today.

IMO, the words stable/unstable add nothing but confusion.

Shai

On Tue, May 4, 2010 at 3:57 AM, Uwe Schindler <[email protected]> wrote:

> I will start tomorrow morning MET to create the branch and merge CTA and
> some other issues made by me - hopefully we have a good name until this
> time. Renaming after the branching is a bad idea, as this makes merge logs
> hard to understand. I will also copy the Hudson configs after creating the
> branch.
>
> After that I am on vacation until next Wednesday, this is why I want to do
> it tomorrow morning!
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
> > -----Original Message-----
> > From: Michael McCandless [mailto:[email protected]]
> > Sent: Tuesday, May 04, 2010 1:32 AM
> > To: [email protected]
> > Subject: Re: [VOTE] Take 2: Open up a separate line for unstable
> > Solr/Lucene development
> >
> > I think maint sends the wrong message, ie, dev should be active (not
> > just maintenance) on the stable branch.
> >
> > We could just do 3x (ie drop "stable_" from it)?
> >
> > Mike
> >
> > On Mon, May 3, 2010 at 6:25 PM, Marvin Humphrey
> > <[email protected]> wrote:
> > > On Mon, May 03, 2010 at 06:21:08PM -0400, Erik Hatcher wrote:
> > >> Can we please not use the word "stable"/"unstable" for these things?
> > >
> > > One possibility: "maint_31", "maint_32", etc.
> > >
> > > Marvin Humphrey
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to