How do we have a release candidate if we still have issues open? Or is this just a test run?
On Mar 7, 2011, at 1:32 AM, Robert Muir wrote: > Hi all, > > I have posted a release candidate for both Lucene 3.1 and Solr 3.1, > both from revision 1078688 of > http://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_3_1/ > Thanks for all your help! Please test them and give your votes, the > tentative release date for both versions is Sunday, March 13th, 2011. > Only votes from Lucene PMC are binding, but everyone is welcome to > check the release candidates and voice their approval or disapproval. > The vote passes if at least three binding +1 votes are cast. > > The release candidates are produced in parallel because in 2010 we > merged the development of Lucene and Solr in order to produce higher > quality releases. While we voted to reserve the right to release > Lucene by itself, in my opinion we should definitely try to avoid this > unless absolutely necessary, as it would ultimately cause more work > and complication: instead it would be far easier to just fix whatever > issues are discovered and respin both releases again. > > Because of this, I ask that you cast a single vote to cover both > releases. If the vote succeeds, both sets of artifacts can go their > separate ways to the different websites. > > Artifacts are located here: http://s.apache.org/solrcene31rc0 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
