Mailing List Archive

Bugfix release Lucene/Solr 8.11.2
To: dev@lucene, dev@solr

NOTICE:

I am planning on preparing a bugfix release from branch branch_8_11 (likely
mid next week)

Please observe the normal rules for committing to this branch:

* Before committing to the branch, reply to this thread and argue
why the fix needs backporting and how long it will take.
** If you're backporting stuff this week still or over the weekend, then
skip
the bit about how long it will take.
* All issues accepted for backporting should be marked with 8.11.2
in JIRA, and issues that should delay the release must be marked as
Blocker
* All patches that are intended for the branch should first be committed
to the unstable branch, merged into the stable branch, and then into
the current release branch.
* Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
a release candidate build.

Also, please observe that since 9.0 already exists, there cannot be any
index format breaking changes. It really should only be bug fixes that have
already been verified on the 9x branch.

Thanks,
Mike
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Thanks for volunteering, Mike!

I think the commits I was tracking to be in 8x are already there, but I'll
confirm this over the weekend and let you know in case I intend to backport
anything more.

On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:

> To: dev@lucene, dev@solr
>
> NOTICE:
>
> I am planning on preparing a bugfix release from branch branch_8_11
> (likely mid next week)
>
> Please observe the normal rules for committing to this branch:
>
> * Before committing to the branch, reply to this thread and argue
> why the fix needs backporting and how long it will take.
> ** If you're backporting stuff this week still or over the weekend, then
> skip
> the bit about how long it will take.
> * All issues accepted for backporting should be marked with 8.11.2
> in JIRA, and issues that should delay the release must be marked as
> Blocker
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
> delay
> a release candidate build.
>
> Also, please observe that since 9.0 already exists, there cannot be any
> index format breaking changes. It really should only be bug fixes that have
> already been verified on the 9x branch.
>
> Thanks,
> Mike
>


--
Anshum Gupta
RE: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Should we maybe also ask on the Lucene side if any backports to 8.11 would be good?



Uwe



-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: uwe@thetaphi.de



From: Anshum Gupta <anshum@anshumgupta.net>
Sent: Friday, May 13, 2022 1:23 AM
To: dev@solr.apache.org
Cc: Solr/Lucene Dev <dev@lucene.apache.org>
Subject: Re: Bugfix release Lucene/Solr 8.11.2



Thanks for volunteering, Mike!



I think the commits I was tracking to be in 8x are already there, but I'll confirm this over the weekend and let you know in case I intend to backport anything more.



On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com <mailto:mdrob@mdrob.com> > wrote:

To: dev@lucene, dev@solr



NOTICE:


I am planning on preparing a bugfix release from branch branch_8_11 (likely mid next week)

Please observe the normal rules for committing to this branch:

* Before committing to the branch, reply to this thread and argue
why the fix needs backporting and how long it will take.

** If you're backporting stuff this week still or over the weekend, then skip

the bit about how long it will take.
* All issues accepted for backporting should be marked with 8.11.2
in JIRA, and issues that should delay the release must be marked as Blocker
* All patches that are intended for the branch should first be committed
to the unstable branch, merged into the stable branch, and then into
the current release branch.
* Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
a release candidate build.



Also, please observe that since 9.0 already exists, there cannot be any index format breaking changes. It really should only be bug fixes that have already been verified on the 9x branch.



Thanks,

Mike






--

Anshum Gupta
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Yes please! I assumed that was already the case as both lists are copied :)

On Fri, May 13, 2022 at 12:47 AM Uwe Schindler <uwe@thetaphi.de> wrote:

> Should we maybe also ask on the Lucene side if any backports to 8.11 would
> be good?
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> https://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* Anshum Gupta <anshum@anshumgupta.net>
> *Sent:* Friday, May 13, 2022 1:23 AM
> *To:* dev@solr.apache.org
> *Cc:* Solr/Lucene Dev <dev@lucene.apache.org>
> *Subject:* Re: Bugfix release Lucene/Solr 8.11.2
>
>
>
> Thanks for volunteering, Mike!
>
>
>
> I think the commits I was tracking to be in 8x are already there, but I'll
> confirm this over the weekend and let you know in case I intend to backport
> anything more.
>
>
>
> On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:
>
> To: dev@lucene, dev@solr
>
>
>
> NOTICE:
>
>
> I am planning on preparing a bugfix release from branch branch_8_11
> (likely mid next week)
>
> Please observe the normal rules for committing to this branch:
>
> * Before committing to the branch, reply to this thread and argue
> why the fix needs backporting and how long it will take.
>
> ** If you're backporting stuff this week still or over the weekend, then
> skip
>
> the bit about how long it will take.
> * All issues accepted for backporting should be marked with 8.11.2
> in JIRA, and issues that should delay the release must be marked as
> Blocker
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
> delay
> a release candidate build.
>
>
>
> Also, please observe that since 9.0 already exists, there cannot be any
> index format breaking changes. It really should only be bug fixes that have
> already been verified on the 9x branch.
>
>
>
> Thanks,
>
> Mike
>
>
>
>
> --
>
> Anshum Gupta
>


--
Anshum Gupta
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
I think it would be good if we can get
https://issues.apache.org/jira/browse/SOLR-16194 into 8.11.2 I plan to work
on it this weekend. I'm hoping it will be a straightforward matter of
adding a check for existing collections.

On Fri, May 13, 2022 at 4:21 AM Anshum Gupta <anshum@anshumgupta.net> wrote:

> Yes please! I assumed that was already the case as both lists are copied
> :)
>
> On Fri, May 13, 2022 at 12:47 AM Uwe Schindler <uwe@thetaphi.de> wrote:
>
>> Should we maybe also ask on the Lucene side if any backports to 8.11
>> would be good?
>>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> https://www.thetaphi.de
>>
>> eMail: uwe@thetaphi.de
>>
>>
>>
>> *From:* Anshum Gupta <anshum@anshumgupta.net>
>> *Sent:* Friday, May 13, 2022 1:23 AM
>> *To:* dev@solr.apache.org
>> *Cc:* Solr/Lucene Dev <dev@lucene.apache.org>
>> *Subject:* Re: Bugfix release Lucene/Solr 8.11.2
>>
>>
>>
>> Thanks for volunteering, Mike!
>>
>>
>>
>> I think the commits I was tracking to be in 8x are already there, but
>> I'll confirm this over the weekend and let you know in case I intend to
>> backport anything more.
>>
>>
>>
>> On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:
>>
>> To: dev@lucene, dev@solr
>>
>>
>>
>> NOTICE:
>>
>>
>> I am planning on preparing a bugfix release from branch branch_8_11
>> (likely mid next week)
>>
>> Please observe the normal rules for committing to this branch:
>>
>> * Before committing to the branch, reply to this thread and argue
>> why the fix needs backporting and how long it will take.
>>
>> ** If you're backporting stuff this week still or over the weekend, then
>> skip
>>
>> the bit about how long it will take.
>> * All issues accepted for backporting should be marked with 8.11.2
>> in JIRA, and issues that should delay the release must be marked as
>> Blocker
>> * All patches that are intended for the branch should first be committed
>> to the unstable branch, merged into the stable branch, and then into
>> the current release branch.
>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>> delay
>> a release candidate build.
>>
>>
>>
>> Also, please observe that since 9.0 already exists, there cannot be any
>> index format breaking changes. It really should only be bug fixes that have
>> already been verified on the 9x branch.
>>
>>
>>
>> Thanks,
>>
>> Mike
>>
>>
>>
>>
>> --
>>
>> Anshum Gupta
>>
>
>
> --
> Anshum Gupta
>


--
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
https://issues.apache.org/jira/browse/SOLR-16194 now has a PR (
https://github.com/apache/solr/pull/864) will commit after review or 3 days
without objections

On Fri, May 13, 2022 at 12:19 PM Gus Heck <gus.heck@gmail.com> wrote:

> I think it would be good if we can get
> https://issues.apache.org/jira/browse/SOLR-16194 into 8.11.2 I plan to
> work on it this weekend. I'm hoping it will be a straightforward matter of
> adding a check for existing collections.
>
> On Fri, May 13, 2022 at 4:21 AM Anshum Gupta <anshum@anshumgupta.net>
> wrote:
>
>> Yes please! I assumed that was already the case as both lists are copied
>> :)
>>
>> On Fri, May 13, 2022 at 12:47 AM Uwe Schindler <uwe@thetaphi.de> wrote:
>>
>>> Should we maybe also ask on the Lucene side if any backports to 8.11
>>> would be good?
>>>
>>>
>>>
>>> Uwe
>>>
>>>
>>>
>>> -----
>>>
>>> Uwe Schindler
>>>
>>> Achterdiek 19, D-28357 Bremen
>>>
>>> https://www.thetaphi.de
>>>
>>> eMail: uwe@thetaphi.de
>>>
>>>
>>>
>>> *From:* Anshum Gupta <anshum@anshumgupta.net>
>>> *Sent:* Friday, May 13, 2022 1:23 AM
>>> *To:* dev@solr.apache.org
>>> *Cc:* Solr/Lucene Dev <dev@lucene.apache.org>
>>> *Subject:* Re: Bugfix release Lucene/Solr 8.11.2
>>>
>>>
>>>
>>> Thanks for volunteering, Mike!
>>>
>>>
>>>
>>> I think the commits I was tracking to be in 8x are already there, but
>>> I'll confirm this over the weekend and let you know in case I intend to
>>> backport anything more.
>>>
>>>
>>>
>>> On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:
>>>
>>> To: dev@lucene, dev@solr
>>>
>>>
>>>
>>> NOTICE:
>>>
>>>
>>> I am planning on preparing a bugfix release from branch branch_8_11
>>> (likely mid next week)
>>>
>>> Please observe the normal rules for committing to this branch:
>>>
>>> * Before committing to the branch, reply to this thread and argue
>>> why the fix needs backporting and how long it will take.
>>>
>>> ** If you're backporting stuff this week still or over the weekend, then
>>> skip
>>>
>>> the bit about how long it will take.
>>> * All issues accepted for backporting should be marked with 8.11.2
>>> in JIRA, and issues that should delay the release must be marked as
>>> Blocker
>>> * All patches that are intended for the branch should first be committed
>>> to the unstable branch, merged into the stable branch, and then into
>>> the current release branch.
>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>>> delay
>>> a release candidate build.
>>>
>>>
>>>
>>> Also, please observe that since 9.0 already exists, there cannot be any
>>> index format breaking changes. It really should only be bug fixes that have
>>> already been verified on the 9x branch.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Mike
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Anshum Gupta
>>>
>>
>>
>> --
>> Anshum Gupta
>>
>
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)
>


--
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
commit and backport of course :)

On Sun, May 15, 2022 at 7:47 PM Gus Heck <gus.heck@gmail.com> wrote:

> https://issues.apache.org/jira/browse/SOLR-16194 now has a PR (
> https://github.com/apache/solr/pull/864) will commit after review or 3
> days without objections
>
> On Fri, May 13, 2022 at 12:19 PM Gus Heck <gus.heck@gmail.com> wrote:
>
>> I think it would be good if we can get
>> https://issues.apache.org/jira/browse/SOLR-16194 into 8.11.2 I plan to
>> work on it this weekend. I'm hoping it will be a straightforward matter of
>> adding a check for existing collections.
>>
>> On Fri, May 13, 2022 at 4:21 AM Anshum Gupta <anshum@anshumgupta.net>
>> wrote:
>>
>>> Yes please! I assumed that was already the case as both lists are copied
>>> :)
>>>
>>> On Fri, May 13, 2022 at 12:47 AM Uwe Schindler <uwe@thetaphi.de> wrote:
>>>
>>>> Should we maybe also ask on the Lucene side if any backports to 8.11
>>>> would be good?
>>>>
>>>>
>>>>
>>>> Uwe
>>>>
>>>>
>>>>
>>>> -----
>>>>
>>>> Uwe Schindler
>>>>
>>>> Achterdiek 19, D-28357 Bremen
>>>>
>>>> https://www.thetaphi.de
>>>>
>>>> eMail: uwe@thetaphi.de
>>>>
>>>>
>>>>
>>>> *From:* Anshum Gupta <anshum@anshumgupta.net>
>>>> *Sent:* Friday, May 13, 2022 1:23 AM
>>>> *To:* dev@solr.apache.org
>>>> *Cc:* Solr/Lucene Dev <dev@lucene.apache.org>
>>>> *Subject:* Re: Bugfix release Lucene/Solr 8.11.2
>>>>
>>>>
>>>>
>>>> Thanks for volunteering, Mike!
>>>>
>>>>
>>>>
>>>> I think the commits I was tracking to be in 8x are already there, but
>>>> I'll confirm this over the weekend and let you know in case I intend to
>>>> backport anything more.
>>>>
>>>>
>>>>
>>>> On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:
>>>>
>>>> To: dev@lucene, dev@solr
>>>>
>>>>
>>>>
>>>> NOTICE:
>>>>
>>>>
>>>> I am planning on preparing a bugfix release from branch branch_8_11
>>>> (likely mid next week)
>>>>
>>>> Please observe the normal rules for committing to this branch:
>>>>
>>>> * Before committing to the branch, reply to this thread and argue
>>>> why the fix needs backporting and how long it will take.
>>>>
>>>> ** If you're backporting stuff this week still or over the weekend,
>>>> then skip
>>>>
>>>> the bit about how long it will take.
>>>> * All issues accepted for backporting should be marked with 8.11.2
>>>> in JIRA, and issues that should delay the release must be marked as
>>>> Blocker
>>>> * All patches that are intended for the branch should first be committed
>>>> to the unstable branch, merged into the stable branch, and then into
>>>> the current release branch.
>>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>>>> delay
>>>> a release candidate build.
>>>>
>>>>
>>>>
>>>> Also, please observe that since 9.0 already exists, there cannot be any
>>>> index format breaking changes. It really should only be bug fixes that have
>>>> already been verified on the 9x branch.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Mike
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Anshum Gupta
>>>>
>>>
>>>
>>> --
>>> Anshum Gupta
>>>
>>
>>
>> --
>> http://www.needhamsoftware.com (work)
>> http://www.the111shift.com (play)
>>
>
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)
>


--
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Thanks Mike for stepping up to do 8.11.2!

We recently uncovered some unexpected behavior with SQL LIKE queries
and I'd like to get a fix for
https://issues.apache.org/jira/browse/SOLR-16199 into 8.11.2. Will be
working on it today / tomorrow.

Cheers,
Tim

On Sun, May 15, 2022 at 5:49 PM Gus Heck <gus.heck@gmail.com> wrote:
>
> commit and backport of course :)
>
> On Sun, May 15, 2022 at 7:47 PM Gus Heck <gus.heck@gmail.com> wrote:
>>
>> https://issues.apache.org/jira/browse/SOLR-16194 now has a PR (https://github.com/apache/solr/pull/864) will commit after review or 3 days without objections
>>
>> On Fri, May 13, 2022 at 12:19 PM Gus Heck <gus.heck@gmail.com> wrote:
>>>
>>> I think it would be good if we can get https://issues.apache.org/jira/browse/SOLR-16194 into 8.11.2 I plan to work on it this weekend. I'm hoping it will be a straightforward matter of adding a check for existing collections.
>>>
>>> On Fri, May 13, 2022 at 4:21 AM Anshum Gupta <anshum@anshumgupta.net> wrote:
>>>>
>>>> Yes please! I assumed that was already the case as both lists are copied :)
>>>>
>>>> On Fri, May 13, 2022 at 12:47 AM Uwe Schindler <uwe@thetaphi.de> wrote:
>>>>>
>>>>> Should we maybe also ask on the Lucene side if any backports to 8.11 would be good?
>>>>>
>>>>>
>>>>>
>>>>> Uwe
>>>>>
>>>>>
>>>>>
>>>>> -----
>>>>>
>>>>> Uwe Schindler
>>>>>
>>>>> Achterdiek 19, D-28357 Bremen
>>>>>
>>>>> https://www.thetaphi.de
>>>>>
>>>>> eMail: uwe@thetaphi.de
>>>>>
>>>>>
>>>>>
>>>>> From: Anshum Gupta <anshum@anshumgupta.net>
>>>>> Sent: Friday, May 13, 2022 1:23 AM
>>>>> To: dev@solr.apache.org
>>>>> Cc: Solr/Lucene Dev <dev@lucene.apache.org>
>>>>> Subject: Re: Bugfix release Lucene/Solr 8.11.2
>>>>>
>>>>>
>>>>>
>>>>> Thanks for volunteering, Mike!
>>>>>
>>>>>
>>>>>
>>>>> I think the commits I was tracking to be in 8x are already there, but I'll confirm this over the weekend and let you know in case I intend to backport anything more.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, May 12, 2022 at 4:03 PM Mike Drob <mdrob@mdrob.com> wrote:
>>>>>
>>>>> To: dev@lucene, dev@solr
>>>>>
>>>>>
>>>>>
>>>>> NOTICE:
>>>>>
>>>>>
>>>>> I am planning on preparing a bugfix release from branch branch_8_11 (likely mid next week)
>>>>>
>>>>> Please observe the normal rules for committing to this branch:
>>>>>
>>>>> * Before committing to the branch, reply to this thread and argue
>>>>> why the fix needs backporting and how long it will take.
>>>>>
>>>>> ** If you're backporting stuff this week still or over the weekend, then skip
>>>>>
>>>>> the bit about how long it will take.
>>>>> * All issues accepted for backporting should be marked with 8.11.2
>>>>> in JIRA, and issues that should delay the release must be marked as Blocker
>>>>> * All patches that are intended for the branch should first be committed
>>>>> to the unstable branch, merged into the stable branch, and then into
>>>>> the current release branch.
>>>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
>>>>> a release candidate build.
>>>>>
>>>>>
>>>>>
>>>>> Also, please observe that since 9.0 already exists, there cannot be any index format breaking changes. It really should only be bug fixes that have already been verified on the 9x branch.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Anshum Gupta
>>>>
>>>>
>>>>
>>>> --
>>>> Anshum Gupta
>>>
>>>
>>>
>>> --
>>> http://www.needhamsoftware.com (work)
>>> http://www.the111shift.com (play)
>>
>>
>>
>> --
>> http://www.needhamsoftware.com (work)
>> http://www.the111shift.com (play)
>
>
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re:Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
https://issues.apache.org/jira/browse/LUCENE-10477 could be backported via https://github.com/apache/lucene-solr/pull/2656 which is ready for review.

Glad to hear there'll be a 8.11.2 release, thanks for volunteering to RM it!

From: dev@lucene.apache.org At: 05/13/22 00:04:02 UTC+1:00To: dev@lucene.apache.org, dev@solr.apache.org
Subject: Bugfix release Lucene/Solr 8.11.2

To: dev@lucene, dev@solr

NOTICE:

I am planning on preparing a bugfix release from branch branch_8_11 (likely mid next week)

Please observe the normal rules for committing to this branch:

* Before committing to the branch, reply to this thread and argue
why the fix needs backporting and how long it will take.
** If you're backporting stuff this week still or over the weekend, then skip
the bit about how long it will take.
* All issues accepted for backporting should be marked with 8.11.2
in JIRA, and issues that should delay the release must be marked as Blocker
* All patches that are intended for the branch should first be committed
to the unstable branch, merged into the stable branch, and then into
the current release branch.
* Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
a release candidate build.

Also, please observe that since 9.0 already exists, there cannot be any index format breaking changes. It really should only be bug fixes that have already been verified on the 9x branch.

Thanks,
Mike
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 <https://issues.apache.org/jira/browse/SOLR-16019> because I have an in-flight PR with a backport. I'll complete and merge that PR.

Jan


> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>
> To: dev@lucene, dev@solr
>
> NOTICE:
>
> I am planning on preparing a bugfix release from branch branch_8_11 (likely mid next week)
>
> Please observe the normal rules for committing to this branch:
>
> * Before committing to the branch, reply to this thread and argue
> why the fix needs backporting and how long it will take.
> ** If you're backporting stuff this week still or over the weekend, then skip
> the bit about how long it will take.
> * All issues accepted for backporting should be marked with 8.11.2
> in JIRA, and issues that should delay the release must be marked as Blocker
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
> a release candidate build.
>
> Also, please observe that since 9.0 already exists, there cannot be any index format breaking changes. It really should only be bug fixes that have already been verified on the 9x branch.
>
> Thanks,
> Mike
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
SOLR-16194 is in and ported to 8.11,.2

On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com> wrote:

> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because
> I have an in-flight PR with a backport. I'll complete and merge that PR.
>
> Jan
>
>
> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>
> To: dev@lucene, dev@solr
>
> NOTICE:
>
> I am planning on preparing a bugfix release from branch branch_8_11
> (likely mid next week)
>
> Please observe the normal rules for committing to this branch:
>
> * Before committing to the branch, reply to this thread and argue
> why the fix needs backporting and how long it will take.
> ** If you're backporting stuff this week still or over the weekend, then
> skip
> the bit about how long it will take.
> * All issues accepted for backporting should be marked with 8.11.2
> in JIRA, and issues that should delay the release must be marked as
> Blocker
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
> delay
> a release candidate build.
>
> Also, please observe that since 9.0 already exists, there cannot be any
> index format breaking changes. It really should only be bug fixes that have
> already been verified on the 9x branch.
>
> Thanks,
> Mike
>
>
>

--
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 <https://issues.apache.org/jira/browse/SOLR-16213> and also backported to 8_11. Wdyt?

Jan

> 18. mai 2022 kl. 15:22 skrev Gus Heck <gus.heck@gmail.com>:
>
> SOLR-16194 is in and ported to 8.11,.2
>
> On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com <mailto:jan.asf@cominvent.com>> wrote:
> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 <https://issues.apache.org/jira/browse/SOLR-16019> because I have an in-flight PR with a backport. I'll complete and merge that PR.
>
> Jan
>
>
>> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com <mailto:mdrob@mdrob.com>>:
>>
>> To: dev@lucene, dev@solr
>>
>> NOTICE:
>>
>> I am planning on preparing a bugfix release from branch branch_8_11 (likely mid next week)
>>
>> Please observe the normal rules for committing to this branch:
>>
>> * Before committing to the branch, reply to this thread and argue
>> why the fix needs backporting and how long it will take.
>> ** If you're backporting stuff this week still or over the weekend, then skip
>> the bit about how long it will take.
>> * All issues accepted for backporting should be marked with 8.11.2
>> in JIRA, and issues that should delay the release must be marked as Blocker
>> * All patches that are intended for the branch should first be committed
>> to the unstable branch, merged into the stable branch, and then into
>> the current release branch.
>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will delay
>> a release candidate build.
>>
>> Also, please observe that since 9.0 already exists, there cannot be any index format breaking changes. It really should only be bug fixes that have already been verified on the 9x branch.
>>
>> Thanks,
>> Mike
>
>
>
> --
> http://www.needhamsoftware.com <http://www.needhamsoftware.com/> (work)
> http://www.the111shift.com <http://www.the111shift.com/> (play)
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Howdy folks, now that Lucene 9.2 has wrapped and we're past the holiday
weekend in the United States, I'd like to take a look at getting this
rolling by the end of the week. I see an open PR for
backporting LUCENE-10236 but it doesn't look like anything else would
really be waiting at the moment.

I will plan to build a release candidate on Thursday (sooner if
LUCENE-10236 is committed, later if somebody else shouts that they have
other issues).

Thanks!

On Tue, May 24, 2022 at 3:48 PM Jan Høydahl <jan.asf@cominvent.com> wrote:

> I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 and
> also backported to 8_11. Wdyt?
>
> Jan
>
> 18. mai 2022 kl. 15:22 skrev Gus Heck <gus.heck@gmail.com>:
>
> SOLR-16194 is in and ported to 8.11,.2
>
> On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com> wrote:
>
>> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because
>> I have an in-flight PR with a backport. I'll complete and merge that PR.
>>
>> Jan
>>
>>
>> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>>
>> To: dev@lucene, dev@solr
>>
>> NOTICE:
>>
>> I am planning on preparing a bugfix release from branch branch_8_11
>> (likely mid next week)
>>
>> Please observe the normal rules for committing to this branch:
>>
>> * Before committing to the branch, reply to this thread and argue
>> why the fix needs backporting and how long it will take.
>> ** If you're backporting stuff this week still or over the weekend, then
>> skip
>> the bit about how long it will take.
>> * All issues accepted for backporting should be marked with 8.11.2
>> in JIRA, and issues that should delay the release must be marked as
>> Blocker
>> * All patches that are intended for the branch should first be committed
>> to the unstable branch, merged into the stable branch, and then into
>> the current release branch.
>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>> delay
>> a release candidate build.
>>
>> Also, please observe that since 9.0 already exists, there cannot be any
>> index format breaking changes. It really should only be bug fixes that have
>> already been verified on the 9x branch.
>>
>> Thanks,
>> Mike
>>
>>
>>
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)
>
>
>
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Hi Mike,

I found a new issue in Solr SQL (SOLR-16227) and have a fix for it (
https://github.com/apache/solr/pull/887). Can you wait on the release for
8.11.2 till I can backport this?

Thank you,
Kiran.

On Tue, May 31, 2022 at 9:21 AM Mike Drob <mdrob@apache.org> wrote:

> Howdy folks, now that Lucene 9.2 has wrapped and we're past the holiday
> weekend in the United States, I'd like to take a look at getting this
> rolling by the end of the week. I see an open PR for
> backporting LUCENE-10236 but it doesn't look like anything else would
> really be waiting at the moment.
>
> I will plan to build a release candidate on Thursday (sooner if
> LUCENE-10236 is committed, later if somebody else shouts that they have
> other issues).
>
> Thanks!
>
> On Tue, May 24, 2022 at 3:48 PM Jan Høydahl <jan.asf@cominvent.com> wrote:
>
>> I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 and
>> also backported to 8_11. Wdyt?
>>
>> Jan
>>
>> 18. mai 2022 kl. 15:22 skrev Gus Heck <gus.heck@gmail.com>:
>>
>> SOLR-16194 is in and ported to 8.11,.2
>>
>> On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com>
>> wrote:
>>
>>> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because
>>> I have an in-flight PR with a backport. I'll complete and merge that PR.
>>>
>>> Jan
>>>
>>>
>>> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>>>
>>> To: dev@lucene, dev@solr
>>>
>>> NOTICE:
>>>
>>> I am planning on preparing a bugfix release from branch branch_8_11
>>> (likely mid next week)
>>>
>>> Please observe the normal rules for committing to this branch:
>>>
>>> * Before committing to the branch, reply to this thread and argue
>>> why the fix needs backporting and how long it will take.
>>> ** If you're backporting stuff this week still or over the weekend, then
>>> skip
>>> the bit about how long it will take.
>>> * All issues accepted for backporting should be marked with 8.11.2
>>> in JIRA, and issues that should delay the release must be marked as
>>> Blocker
>>> * All patches that are intended for the branch should first be committed
>>> to the unstable branch, merged into the stable branch, and then into
>>> the current release branch.
>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>>> delay
>>> a release candidate build.
>>>
>>> Also, please observe that since 9.0 already exists, there cannot be any
>>> index format breaking changes. It really should only be bug fixes that have
>>> already been verified on the 9x branch.
>>>
>>> Thanks,
>>> Mike
>>>
>>>
>>>
>>
>> --
>> http://www.needhamsoftware.com (work)
>> http://www.the111shift.com (play)
>>
>>
>>
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
Yes, please fix and backport SOLR-16227, it looks almost ready from the
conversation on the PR. I will plan to do the first RC on Monday if we can
get the backport completed today.

On Thu, Jun 2, 2022 at 9:18 AM kiran chitturi <chitturikiran15@gmail.com>
wrote:

> Hi Mike,
>
> I found a new issue in Solr SQL (SOLR-16227) and have a fix for it (
> https://github.com/apache/solr/pull/887). Can you wait on the release for
> 8.11.2 till I can backport this?
>
> Thank you,
> Kiran.
>
> On Tue, May 31, 2022 at 9:21 AM Mike Drob <mdrob@apache.org> wrote:
>
>> Howdy folks, now that Lucene 9.2 has wrapped and we're past the holiday
>> weekend in the United States, I'd like to take a look at getting this
>> rolling by the end of the week. I see an open PR for
>> backporting LUCENE-10236 but it doesn't look like anything else would
>> really be waiting at the moment.
>>
>> I will plan to build a release candidate on Thursday (sooner if
>> LUCENE-10236 is committed, later if somebody else shouts that they have
>> other issues).
>>
>> Thanks!
>>
>> On Tue, May 24, 2022 at 3:48 PM Jan Høydahl <jan.asf@cominvent.com>
>> wrote:
>>
>>> I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 and
>>> also backported to 8_11. Wdyt?
>>>
>>> Jan
>>>
>>> 18. mai 2022 kl. 15:22 skrev Gus Heck <gus.heck@gmail.com>:
>>>
>>> SOLR-16194 is in and ported to 8.11,.2
>>>
>>> On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com>
>>> wrote:
>>>
>>>> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because
>>>> I have an in-flight PR with a backport. I'll complete and merge that PR.
>>>>
>>>> Jan
>>>>
>>>>
>>>> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>>>>
>>>> To: dev@lucene, dev@solr
>>>>
>>>> NOTICE:
>>>>
>>>> I am planning on preparing a bugfix release from branch branch_8_11
>>>> (likely mid next week)
>>>>
>>>> Please observe the normal rules for committing to this branch:
>>>>
>>>> * Before committing to the branch, reply to this thread and argue
>>>> why the fix needs backporting and how long it will take.
>>>> ** If you're backporting stuff this week still or over the weekend,
>>>> then skip
>>>> the bit about how long it will take.
>>>> * All issues accepted for backporting should be marked with 8.11.2
>>>> in JIRA, and issues that should delay the release must be marked as
>>>> Blocker
>>>> * All patches that are intended for the branch should first be committed
>>>> to the unstable branch, merged into the stable branch, and then into
>>>> the current release branch.
>>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>>>> delay
>>>> a release candidate build.
>>>>
>>>> Also, please observe that since 9.0 already exists, there cannot be any
>>>> index format breaking changes. It really should only be bug fixes that have
>>>> already been verified on the 9x branch.
>>>>
>>>> Thanks,
>>>> Mike
>>>>
>>>>
>>>>
>>>
>>> --
>>> http://www.needhamsoftware.com (work)
>>> http://www.the111shift.com (play)
>>>
>>>
>>>
Re: Bugfix release Lucene/Solr 8.11.2 [ In reply to ]
I merged SOLR-16227 to main, 9, 8.11 some minutes ago.

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Fri, Jun 3, 2022 at 1:59 PM Mike Drob <mdrob@mdrob.com> wrote:

> Yes, please fix and backport SOLR-16227, it looks almost ready from the
> conversation on the PR. I will plan to do the first RC on Monday if we can
> get the backport completed today.
>
> On Thu, Jun 2, 2022 at 9:18 AM kiran chitturi <chitturikiran15@gmail.com>
> wrote:
>
>> Hi Mike,
>>
>> I found a new issue in Solr SQL (SOLR-16227) and have a fix for it (
>> https://github.com/apache/solr/pull/887). Can you wait on the release
>> for 8.11.2 till I can backport this?
>>
>> Thank you,
>> Kiran.
>>
>> On Tue, May 31, 2022 at 9:21 AM Mike Drob <mdrob@apache.org> wrote:
>>
>>> Howdy folks, now that Lucene 9.2 has wrapped and we're past the holiday
>>> weekend in the United States, I'd like to take a look at getting this
>>> rolling by the end of the week. I see an open PR for
>>> backporting LUCENE-10236 but it doesn't look like anything else would
>>> really be waiting at the moment.
>>>
>>> I will plan to build a release candidate on Thursday (sooner if
>>> LUCENE-10236 is committed, later if somebody else shouts that they have
>>> other issues).
>>>
>>> Thanks!
>>>
>>> On Tue, May 24, 2022 at 3:48 PM Jan Høydahl <jan.asf@cominvent.com>
>>> wrote:
>>>
>>>> I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 and
>>>> also backported to 8_11. Wdyt?
>>>>
>>>> Jan
>>>>
>>>> 18. mai 2022 kl. 15:22 skrev Gus Heck <gus.heck@gmail.com>:
>>>>
>>>> SOLR-16194 is in and ported to 8.11,.2
>>>>
>>>> On Wed, May 18, 2022 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com>
>>>> wrote:
>>>>
>>>>> I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because
>>>>> I have an in-flight PR with a backport. I'll complete and merge that PR.
>>>>>
>>>>> Jan
>>>>>
>>>>>
>>>>> 13. mai 2022 kl. 01:03 skrev Mike Drob <mdrob@mdrob.com>:
>>>>>
>>>>> To: dev@lucene, dev@solr
>>>>>
>>>>> NOTICE:
>>>>>
>>>>> I am planning on preparing a bugfix release from branch branch_8_11
>>>>> (likely mid next week)
>>>>>
>>>>> Please observe the normal rules for committing to this branch:
>>>>>
>>>>> * Before committing to the branch, reply to this thread and argue
>>>>> why the fix needs backporting and how long it will take.
>>>>> ** If you're backporting stuff this week still or over the weekend,
>>>>> then skip
>>>>> the bit about how long it will take.
>>>>> * All issues accepted for backporting should be marked with 8.11.2
>>>>> in JIRA, and issues that should delay the release must be marked as
>>>>> Blocker
>>>>> * All patches that are intended for the branch should first be
>>>>> committed
>>>>> to the unstable branch, merged into the stable branch, and then into
>>>>> the current release branch.
>>>>> * Only Jira issues with Fix version 8.11.2 and priority "Blocker" will
>>>>> delay
>>>>> a release candidate build.
>>>>>
>>>>> Also, please observe that since 9.0 already exists, there cannot be
>>>>> any index format breaking changes. It really should only be bug fixes that
>>>>> have already been verified on the 9x branch.
>>>>>
>>>>> Thanks,
>>>>> Mike
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> http://www.needhamsoftware.com (work)
>>>> http://www.the111shift.com (play)
>>>>
>>>>
>>>>