Re: 6.4.2 release?

[Ishan Chattopadhyaya]

FYI. A new blocker bug was identified, SOLR-10215, and I'm holding off on
the RC until this one is addressed.

On Mon, Feb 27, 2017 at 8:57 PM, Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:

> 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
>>
>>
>

Re: 6.4.2 release?

[Christine Poerschke (BLOOMBERG/ LONDON)]

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 

Re: 6.4.2 release?

[Christine Poerschke (BLOOMBERG/ LONDON)]

Thanks Steve for the guidance!

Since LUCENE-7676 and SOLR-10083 were both (unreleased) 6.5.0 to 6.4.2 
backports I have gone ahead and moved the CHANGES.txt entries on both branch_6x 
and master (after the branch_6_4 commit itself).

My plan for https://issues.apache.org/jira/browse/SOLR-10192 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/ LONDON) 
> <cpoersc...@bloomberg.net> 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 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?

It’s typically a mess: some people move CHANGES entries on the unstable and 
stable branches when they backport to point releases, some don't.  There’s a 
TODO item for the release manager to sync CHANGES post-release: 
<https://wiki.apache.org/lucene-java/ReleaseTodo#Synchronize_CHANGES.txt>.

It’s complicated by the fact that entries should never be removed from 
*released* versions, so issues backported to a point release for an older 
branch typically don’t ever trigger *removal* of duplicate entries elsewhere, 
just copy/paste of the point release’s section into the stable & unstable 
branches’ CHANGES.

--
Steve
www.lucidworks.com
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 6.4.2 release?

[Steve Rowe]

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 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?

It’s typically a mess: some people move CHANGES entries on the unstable and 
stable branches when they backport to point releases, some don't.  There’s a 
TODO item for the release manager to sync CHANGES post-release: 
.

It’s complicated by the fact that entries should never be removed from 
*released* versions, so issues backported to a point release for an older 
branch typically don’t ever trigger *removal* of duplicate entries elsewhere, 
just copy/paste of the point release’s section into the stable & unstable 
branches’ CHANGES.

--
Steve
www.lucidworks.com
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 6.4.2 release?

[Christine Poerschke (BLOOMBERG/ LONDON)]

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: dev@lucene.apache.org
To: dev@lucene.apache.org
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 <ere.maij...@helsinki.fi> 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
>> <ichattopadhy...@gmail.com <mailto:ichattopadhy...@gmail.com>> 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 <jpou...@gmail.com
>> <mailto: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
>> <mailto: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
>> <mailto:cpoersc...@bloomberg.net>> 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: dev@lucene.apache.org
>> <mailto: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
>>
>>
>>
>
> --
> Ere Maijala
> Kansalliskirjasto / The National Library of Finland
>
> -
> 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

Re: 6.4.2 release?

[Michael McCandless]

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 <ere.maij...@helsinki.fi> 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
>> <ichattopadhy...@gmail.com <mailto:ichattopadhy...@gmail.com>> 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 <jpou...@gmail.com
>> <mailto: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
>> <mailto: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
>> <mailto:cpoersc...@bloomberg.net>> 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: dev@lucene.apache.org
>> <mailto: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
>>
>>
>>
>
> --
> Ere Maijala
> Kansalliskirjasto / The National Library of Finland
>
> -
> 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

Re: 6.4.2 release?

[Ishan Chattopadhyaya]

Done.

On Wed, Feb 22, 2017 at 12:04 PM, Ere Maijala <ere.maij...@helsinki.fi>
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
>> <ichattopadhy...@gmail.com <mailto:ichattopadhy...@gmail.com>> 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 <jpou...@gmail.com
>> <mailto: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
>> <mailto: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
>> <mailto:cpoersc...@bloomberg.net>> 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: dev@lucene.apache.org
>> <mailto: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
>>
>>
>>
>>
> --
> Ere Maijala
> Kansalliskirjasto / The National Library of Finland
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: 6.4.2 release?

[Ere Maijala]

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
<ichattopadhy...@gmail.com <mailto:ichattopadhy...@gmail.com>> 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 <jpou...@gmail.com
<mailto: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
<mailto: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
<mailto:cpoersc...@bloomberg.net>> 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: dev@lucene.apache.org
<mailto: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





--
Ere Maijala
Kansalliskirjasto / The National Library of Finland

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 6.4.2 release?

[Ishan Chattopadhyaya]

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 <
ichattopadhy...@gmail.com> 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 <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
>>
>>
>

Re: 6.4.2 release?

[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 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
>
>

6.4.2 release?

[Ere Maijala]

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 I just joined the list.


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




-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 6.4.2 release?

[Adrien Grand]

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

Re: 6.4.2 release?

[Adrien Grand]

+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
>
>

Re:6.4.2 release?

[Christine Poerschke (BLOOMBERG/ LONDON)]

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  

6.4.2 release?

[Andrzej Białecki]

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