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
/ 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
is to have it in
the 6.4.2 section from the outset (if it goes into the 6.4.2 release that is).
Christine
- Original Message -
From: dev@lucene.apache.org
To: dev@lucene.apache.org
At: 02/22/17 13:42:54
Hi Christine,
> On Feb 22, 2017, at 5:10 AM, Christine Poerschke (BLOOMBERG/ LON
Hi Christine,
> On Feb 22, 2017, at 5:10 AM, Christine Poerschke (BLOOMBERG/ LONDON)
> wrote:
>
> 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
eless 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 discuss
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.
gt; 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
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
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
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
Hi,
I'd like to nominate LUCENE-7698 (CommonGramsQueryFilter doesn't work
properly, caused by LUCENE-7603 and a regression from 6.3.0 where it
worked fine). It doesn't have a fix, but at least we got seriously
bitten by it.
Regards,
Ere
P.S. Sorry, no proper references in this email since
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-10
-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
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
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
15 matches
Mail list logo