Hi Shalin, Since we must re-spin for LUCENE-7501 (I'm still working on that), is it OK if I backport LUCENE-7135 for 6.3.0?
At least, I need to fix the CHANGES.txt entry if not. Mike McCandless http://blog.mikemccandless.com On Tue, Nov 1, 2016 at 5:19 PM, Michael McCandless <luc...@mikemccandless.com> wrote: > I think there's possibly a bad problem with LUCENE-7501 (creates a > possibly corrupt index) ... I'm trying to dig more to be sure ... > > Mike McCandless > > http://blog.mikemccandless.com > > On Mon, Oct 31, 2016 at 2:28 PM, Shalin Shekhar Mangar > <sha...@apache.org> wrote: >> Please vote for the second release candidate for Lucene/Solr 6.3.0 >> >> The artifacts can be downloaded from: >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.3.0-RC2-rev1fe1a54db32b8c27bfae81887cd4d75242090613/ >> >> You can run the smoke tester directly with this command: >> python3 -u dev-tools/scripts/smokeTestRelease.py >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.3.0-RC2-rev1fe1a54db32b8c27bfae81887cd4d75242090613/ >> >> Smoke tester passed for me: >> SUCCESS! [0:35:05.847870] >> >> Here's my +1 to release. >> >> -- >> Regards, >> Shalin Shekhar Mangar. >> >> --------------------------------------------------------------------- >> 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
