Thanks Simon! Sorry about that - I hate to cause more work for anyone. - Mark
On Nov 19, 2013, at 5:01 AM, Simon Willnauer <[email protected]> wrote: > I guess that means yet another RC. I call this vote as failed and > build a new RC. > > simon > > On Tue, Nov 19, 2013 at 4:48 AM, Mark Miller <[email protected]> wrote: >> I guess I voted a little too soon… >> >> I hate to be the cause of a respin, but while looking into a few things I >> noticed while fixing that bug over the weekend, I found that what I thought >> was not that critical of a bug was actually masking a couple fairly ugly >> bugs and was fairly dangerous itself. >> >> Together, I think all 3 are actually quite serious problems and 2 of them >> are new in 4.6. I think they are worthy of a respin. >> >> I’m going to back port them, but if people would rather not respin, they can >> wait on the branch for 4.6.1. >> >> - Mark >> >> On Nov 18, 2013, at 7:32 PM, Mark Miller <[email protected]> wrote: >> >>> +1 >>> >>> - Mark >>> >>> On Nov 18, 2013, at 9:22 AM, Simon Willnauer <[email protected]> >>> wrote: >>> >>>> Please vote for the first Release Candidate for Lucene/Solr 4.6.0 >>>> >>>> This RC includes some additional fixes related to Changes.html that >>>> were committed in the last days like SOLR-5397. >>>> >>>> you can download it here: >>>> http://people.apache.org/~simonw/staging_area/lucene-solr-4.6.0-RC3-rev1542975/ >>>> >>>> or run the smoke tester directly with this commandline (don't forget >>>> to set JAVA6_HOME etc.): >>>> >>>> python3.2 -u dev-tools/scripts/smokeTestRelease.py >>>> http://people.apache.org/~simonw/staging_area/lucene-solr-4.6.0-RC3-rev1542975/ >>>> 1542975 4.6.0 /tmp/smoke_test_4_6 >>>> >>>> I integrated the RC into Elasticsearch and all tests pass: >>>> >>>> https://github.com/s1monw/elasticsearch/tree/upgrade_lucene_4_6 >>>> >>>> Smoketester said: SUCCESS! [1:02:10.493223] >>>> >>>> here is my +1 >>>> >>>> --------------------------------------------------------------------- >>>> 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]
