Yeah, I think so? How about naming it stable_3x?
Mike On Mon, May 3, 2010 at 5:44 PM, Uwe Schindler <[email protected]> wrote: > So you mean the Tag as branch? > > ----- > 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: Monday, May 03, 2010 11:40 PM >> To: [email protected] >> Subject: Re: [VOTE] Take 2: Open up a separate line for unstable >> Solr/Lucene development >> >> How about we cut the stable branch from just before flex landed? >> >> Then we can revert any changes from stable, and port back any changes >> from unstable/trunk, over time. >> >> Mike >> >> On Fri, Apr 30, 2010 at 3:18 PM, Steven A Rowe <[email protected]> wrote: >> > March 23: Create new Lu-Solr development folder >> > <http://svn.apache.org/viewvc?view=revision&revision=926572> >> > >> > April 6: LUCENE-2370: Reintegrate flex_1458 branch into trunk >> (revision 931101) >> > <http://svn.apache.org/viewvc?view=revision&revision=931278> >> > >> > On 04/30/2010 at 3:00 PM, Shai Erera wrote: >> >> I would take the last rev just before the first rev when flex >> landed, >> >> so that in includes as much as possible. I don't know though which >> rev >> >> is it and whether it was before/after the lucene/solr merge. >> >> >> >> Shai >> >> >> >> On Friday, April 30, 2010, Chris Hostetter >> <[email protected]> >> >> wrote: >> >> > >> >> > > * Cut a stable branch off of trunk back before flex landed. >> Does >> >> > > anyone have any suggestions of which rev...? >> >> > >> >> > shouldn't this just be the same as the >> lucene/java/branches/lucene_3_0 >> >> > branch that already exists? ... but with solr merged in? >> >> > >> >> > >> >> > >> >> > -Hoss >> >> > >> >> > >> >> > ------------------------------------------------------------------ >> --- >> >> > 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] >> > >> > >> >> --------------------------------------------------------------------- >> 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]
