Hi Bruno,
I'd like to get SOLR-14599 in. It is for the package manager CLI support
for cluster level (core container) level plugins. I think it is important
to have this in 8.6 for two reasons:

(a) it will unblock Marcus Eagan/Ke Zhenxu who are working on a new Solr UI
package and would like to have their package released for early feedback
(b) Earlier we can release this, more feedback we can get before this is
released in 9.0.
(c) This is an isolated change to the CLI for the package manager
(experimental), so very low risk to stability of the release.

I should be done with this issue by eod today. In case you have no
objection, I would like to merge this issue after you cut the branch today
(and before you spin the RC).

Regards,
Ishan

On Tue, Jun 30, 2020 at 6:20 AM Joel Bernstein <joels...@gmail.com> wrote:

> Hi Bruno,
>
> Andrzej and I decided that SOLR-14537 is headed to master to bake for a
> while and won't make it into the 8.6 release. So please feel free to cut
> the branch when ready.
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
> On Mon, Jun 29, 2020 at 6:13 AM Andrzej Białecki <a...@getopt.org> wrote:
>
>> I wold like to include SOLR-14537 in 8.6 (it’s already tagged), the patch
>> is ready and I’m just waiting for Joel to finish performance testing.
>>
>> On 27 Jun 2020, at 04:59, Tomás Fernández Löbbe <tomasflo...@gmail.com>
>> wrote:
>>
>> I tagged SOLR-14590 for 8.6, The PR is ready for review and I plan to
>> merge it soon
>>
>> On Fri, Jun 26, 2020 at 12:54 PM Andrzej Białecki <a...@getopt.org> wrote:
>>
>>> Jan,
>>>
>>> I just removed SOLR-14182 from 8.6, this needs proper back-compat shims
>>> and testing, and I don’t have enough time to get it done properly for 8.6.
>>>
>>> On 26 Jun 2020, at 13:37, Jan Høydahl <jan....@cominvent.com> wrote:
>>>
>>> Unresolved Solr issues tagged with 8.6:
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SOLR%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%208.6
>>> <https://issues.apache.org/jira/issues/?jql=project%20=%20SOLR%20AND%20resolution%20=%20Unresolved%20AND%20fixVersion%20=%208.6>
>>>
>>>
>>> SOLR-14593   Package store API to disable file upload over HTTP
>>>          Blocker
>>> SOLR-14580   CloudSolrClient cannot be initialized using 'zkHosts'
>>> builder       Blocker
>>> SOLR-14516   NPE during Realtime GET
>>>         Major
>>> SOLR-14502   increase bin/solr's post kill sleep
>>>         Minor
>>> SOLR-14398   package store PUT should be idempotent
>>>          Trivial
>>> SOLR-14311   Shared schema should not have access to core level classes
>>>          Major
>>> SOLR-14182   Move metric reporters config from solr.xml to ZK cluster
>>> properties Major
>>> SOLR-14066   Deprecate DIH
>>>         Blocker
>>> SOLR-14022   Deprecate CDCR from Solr in 8.x
>>>         Blocker
>>>
>>> Plus two private JIRA issues.
>>>
>>> Jan
>>>
>>> 26. jun. 2020 kl. 12:06 skrev Bruno Roustant <bruno.roust...@gmail.com>:
>>>
>>> So the plan is to cut the release branch on next Tuesday June 30th. If
>>> you anticipate a problem with the date, please reply.
>>>
>>> Is there any JIRA issue that must be committed before the release is
>>> made and that has not already the appropriate "Fix Version"?
>>>
>>> Currently there 3 unresolved issues flagged as Fix Version = 8.6:
>>> Add tests for corruptions caused by byte flips LUCENE-9356
>>> <https://issues.apache.org/jira/browse/LUCENE-9356>
>>> Fix linefiledocs compression or replace in tests LUCENE-9191
>>> <https://issues.apache.org/jira/browse/LUCENE-9191>
>>> Can we merge small segments during refresh, for faster searching?
>>> LUCENE-8962 <https://issues.apache.org/jira/browse/LUCENE-8962>
>>>
>>>
>>> Le mer. 24 juin 2020 à 21:05, David Smiley <david.w.smi...@gmail.com> a
>>> écrit :
>>>
>>>> Thanks starting this discussion, Cassandra.
>>>>
>>>> I reviewed the issues I was involved with and I don't quite see
>>>> something worth noting.
>>>>
>>>> I plan to add a note about a change in defaults within
>>>> UnifiedHighlighter that could be a significant perf regression.  This
>>>> wasn't introduced in 8.6 but introduced in 8.5 and it's significant enough
>>>> to bring attention to.  I could add it in 8.5's section but then add a
>>>> short pointer to it in 8.6.
>>>>
>>>> ~ David
>>>>
>>>>
>>>> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett <
>>>> casstarg...@gmail.com> wrote:
>>>>
>>>>> I started looking at the Ref Guide for 8.6 to get it ready, and notice
>>>>> there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it
>>>>> really true that none are needed at all?
>>>>>
>>>>> I’ll add what I usually do about new features/changes that maybe
>>>>> wouldn’t normally make the old Upgrade Notes section, I just find it
>>>>> surprising that there weren’t any devs who thought any of the 100 or so
>>>>> Solr changes warrant any user caveats.
>>>>> On Jun 17, 2020, 12:27 PM -0500, Tomás Fernández Löbbe <
>>>>> tomasflo...@gmail.com>, wrote:
>>>>>
>>>>> +1. Thanks Bruno
>>>>>
>>>>> On Wed, Jun 17, 2020 at 6:22 AM Mike Drob <md...@apache.org> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> The release wizard python script should be sufficient for everything.
>>>>>> If you run into any issues with it, let me know, I used it for 8.5.2 and
>>>>>> think I understand it pretty well.
>>>>>>
>>>>>> On Tue, Jun 16, 2020 at 8:31 AM Bruno Roustant <
>>>>>> bruno.roust...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> It’s been a while since we released Lucene/Solr 8.5.
>>>>>>> I’d like to volunteer to be a release manager for an 8.6 release. If
>>>>>>> there's agreement, then I plan to cut the release branch two weeks 
>>>>>>> today,
>>>>>>> on June 30th, and then to build the first RC two days later.
>>>>>>>
>>>>>>> This will be my first time as release manager so I'll probably need
>>>>>>> some guidance. Currently I have two resource links on this subject:
>>>>>>> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
>>>>>>>
>>>>>>> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
>>>>>>> If you have more, please share with me.
>>>>>>>
>>>>>>> Bruno
>>>>>>>
>>>>>>
>>>
>>>
>>

Reply via email to