https://issues.apache.org/jira/browse/SOLR-10192 copy/paste fix just backported 
to branch_6_4 but happy to revert if there were to be any concerns about it.

Thanks,
Christine

From: ichattopadhy...@gmail.com At: 02/21/17 18:05:35
To: dev@lucene.apache.org
Cc: Christine Poerschke (BLOOMBERG/ LONDON)
Subject: Re: 6.4.2 release?

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 <jpou...@gmail.com> 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 <jpou...@gmail.com> 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) 
<cpoersc...@bloomberg.net> a écrit :

Hi,

These two could be minor candidates for inclusion:

* https://issues.apache.org/jira/browse/SOLR-10083
  Fix instanceof check in ConstDoubleSource.equals

* 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: dev@lucene.apache.org At: 02/15/17 14:27:52
To: dev@lucene.apache.org
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 


Reply via email to