Anhum, Minutes ago I went and committed https://issues.apache.org/jira/browse/LUCENE-7417 to master, branch_6x, branch_5x, and branch_5_5. While on both the v5 branches, I noticed the last 5.5.x was specifically 5.5.2 so I went and added this under a new 5.5.3. That is now committed. Then the realization hits me that you're doing a 5.5.3 release and it just passed a vote So I guess I should change those entries to be 5.5.4 and probably also add a blank 5.5.3 section so it's clear there were not additions in 5.5.3 for Lucene? BTW I think this bug is "minor" IMO. ~ David
On Thu, Sep 8, 2016 at 1:29 PM Anshum Gupta <[email protected]> wrote: > The release notes (draft) can be found here: > > Lucene: https://wiki.apache.org/lucene-java/ReleaseNote553 > Solr: https://wiki.apache.org/solr/ReleaseNote553 > > Please feel free to edit/fix it. > > -Anshum > > On Wed, Jul 20, 2016 at 1:35 PM David Smiley <[email protected]> > wrote: > >> Okay. BTW SOLR-9290 isn't "Just" high indexing rates, but it's for those >> using SSL too -- correct me if I'm wrong. We don't want to raise alarm >> bells too loudly :-) >> >> On Wed, Jul 20, 2016 at 4:18 PM Anshum Gupta <[email protected]> >> wrote: >> >>> Hi, >>> >>> With SOLR-9290 fixed, I think it calls for a bug fix release as it >>> impacts all users with high indexing rates. >>> >>> If someone else wants to work on the release, I am fine with it else, >>> I'll be happy to be the RM and cut an RC a week from now. >>> >>> -- >>> Anshum Gupta >>> >> -- >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: >> http://www.solrenterprisesearchserver.com >> > -- Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
