Having some interest in this issue, may I suggest setting a branch date? On the agreed-upon date, a branch is made. After that date, commits go to trunk and (maybe) are pulled up into the 4.0 branch. If the date is oh, say, 1 week away, people can plan accordingly to yield a relatively stable branch right out of the gate.
Karl -----Original Message----- From: ext Robert Muir [mailto:[email protected]] Sent: Wednesday, January 11, 2012 3:15 PM To: [email protected] Cc: [email protected] Subject: Re: Lucene 4.0 Beta On Wed, Jan 11, 2012 at 3:07 PM, Michael McCandless <[email protected]> wrote: > > I'd think we could cut a 4.0 alpha today, after branching. > How? the packaging for modules is totally hosed for example: how would we even package such a thing? Also when we push out alpha/beta/etc shouldn't we at the minimum say 'apis might change but this is the index format' ? Otherwise how is it different than a nightly build to end-users? These are reasons why we must branch: because at any time we should be able to add new packages (like LUCENE-3305) that will 'destabilize' packaging (which is important to get right here), or we might change the index format (like LUCENE-3687) which I think we might not necessarily want to do. (I listed two issues that I feel are very close to being committed right now as examples) -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
