This is a vote for the proposal discussed on the 'Proposal about
Version API relaxation' thread.
The vote is to open up a separate parallel line of development, called
unstable (on trunk), where non-back-compatible changes, slated for the
next major release, may be safely developed.
But it's not
On 4/26/10 8:54 AM, Michael McCandless wrote:
Please vote!
+1
--
- Mark
http://www.lucidimagination.com
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Mon, Apr 26, 2010 at 8:54 AM, Michael McCandless
luc...@mikemccandless.com wrote:
Changes that go into stable need to be merged forwards to unstable --
this may happen commit by commit, or be periodically swept, or some
combination (like flex) -- we can hash out this logistical detail out
Hi,
This is a vote for the proposal discussed on the 'Proposal about
Version API relaxation' thread.
The vote is to open up a separate parallel line of development, called
unstable (on trunk), where non-back-compatible changes, slated for the
next major release, may be safely developed.
OK let's cancel this vote.
I'll change the proposal, to dev on trunk and port back to stable, and
call a new vote.
Mike
On Mon, Apr 26, 2010 at 11:51 AM, Shai Erera ser...@gmail.com wrote:
I'm also -1 on that particular point. I think that dev should happen on
trunk always, and backporting is
