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 <md...@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....@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.h...@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....@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 <md...@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)
>>
>>
>>

Reply via email to