I'm happy to backport LUCENE-7676 and SOLR-10083 from branch_6x to branch_6_4 today.
What process do people typically follow w.r.t. updating CHANGES.txt on branch_6x and master in those circumstances e.g. do the entries move from the 6.5 to the 6.4.2 section or are they duplicated in the 6.4.2 section or is it taken care of somehow overall (for master and branch_6x but not branch_6_4) as part of the RC process? Christine ----- Original Message ----- From: [email protected] To: [email protected] At: 02/22/17 09:59:49 Thanks Ere, I agree LUCENE-7698 should be committed for 6.4.2 ... I'll push & backport today. Mike McCandless http://blog.mikemccandless.com On Wed, Feb 22, 2017 at 1:34 AM, Ere Maijala <[email protected]> wrote: > Please make LUCENE-7698 a blocker if possible. It's a regression that makes > Solr pretty much useless for anyone with CommonGramsQueryFilter in the > analysis chain. > > --Ere > > 21.2.2017, 21.46, Ishan Chattopadhyaya kirjoitti: >> >> Actually, LUCENE-7698 was not a blocker, just marked for a 6.4.2 >> release. Should we make it a blocker? >> As per an offline discussion with Andrzej, I've added SOLR-10182 as a >> blocker. Tentatively, I'll cut a RC for 6.4.2 by Tuesday. >> >> On Tue, Feb 21, 2017 at 11:35 PM, Ishan Chattopadhyaya >> <[email protected] <mailto:[email protected]>> wrote: >> >> I would like to volunteer for this 6.4.2 release. Planning to cut a >> RC as soon as blockers are resolved. >> One of the unresolved blocker issues seems to be LUCENE-7698 (I'll >> take a look to see if there are more). If there are more issues that >> should be part of the release, please let me know or mark as >> blockers in jira. >> >> Thanks, >> Ishan >> >> >> On Thu, Feb 16, 2017 at 3:48 AM, Adrien Grand <[email protected] >> <mailto:[email protected]>> wrote: >> >> I had initially planned on releasing tomorrow but the mirrors >> replicated faster than I had thought they would so I finished >> the release today, including the addition of the new 5.5.4 >> indices for backward testing so I am good with proceeding with a >> new release now. >> >> Le mer. 15 févr. 2017 à 16:13, Adrien Grand <[email protected] >> <mailto:[email protected]>> a écrit : >> >> +1 >> >> One ask I have is to wait for the 5.5.4 release process to >> be complete so that branch_6_4 has the 5.5.4 backward >> indices when we cut the first RC. I will let you know when I >> am done. >> >> Le mer. 15 févr. 2017 à 15:53, Christine Poerschke >> (BLOOMBERG/ LONDON) <[email protected] >> <mailto:[email protected]>> a écrit : >> >> Hi, >> >> These two could be minor candidates for inclusion: >> >> * https://issues.apache.org/jira/browse/SOLR-10083 >> <https://issues.apache.org/jira/browse/SOLR-10083> >> Fix instanceof check in ConstDoubleSource.equals >> >> * https://issues.apache.org/jira/browse/LUCENE-7676 >> <https://issues.apache.org/jira/browse/LUCENE-7676> >> FilterCodecReader to override more super-class methods >> >> The former had narrowly missed the 6.4.1 release. >> >> Regards, >> >> Christine >> >> From: [email protected] >> <mailto:[email protected]> At: 02/15/17 14:27:52 >> To: [email protected] >> Subject: Re:6.4.2 release? >> >> Hi devs, >> >> These two issues seem serious enough to warrant a >> new release from branch_6_4: >> * SOLR-10130: Serious performance degradation in >> Solr 6.4.1 due to the new metrics collection >> * SOLR-10138: Transaction log replay can hit an NPE >> due to new Metrics code. >> >> What do you think? Anything else that should go there? >> >> --- >> Best regards, >> >> Andrzej Bialecki >> >> >> > > -- > Ere Maijala > Kansalliskirjasto / The National Library of Finland > > --------------------------------------------------------------------- > 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]
