It was not urgent. I think we are too late for any new addition. I
shall add it to the next release

On Tue, Jul 7, 2020 at 11:12 PM Noble Paul <[email protected]> wrote:
>
> I would like to commit
> https://issues.apache.org/jira/browse/SOLR-14634 as well please
>
> On Tue, Jul 7, 2020 at 6:04 PM Bruno Roustant <[email protected]> 
> wrote:
> >
> > Thank you for taking care of the unresolved issues. Now it's clean and I'll 
> > start the RC process today (with the help of the Great Release Wizard).
> >
> > For those who want to have a look at the draft release notes (or edit them):
> > Lucene: 
> > https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=158865929&draftShareId=e7da54c5-8e1c-4228-b9f7-ff03ab882080&src=shareui&src.shareui.timestamp=1594107478794
> > Solr: 
> > https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=158865919&draftShareId=9cd1341c-bf4d-4714-b71b-08a685053f4d&src=shareui&src.shareui.timestamp=1594039624215
> >
> > Le lun. 6 juil. 2020 à 20:58, Eric Pugh <[email protected]> a 
> > écrit :
> >>
> >> I just resolved SOLR-14422.
> >>
> >> On Jul 6, 2020, at 1:36 PM, Tomás Fernández Löbbe <[email protected]> 
> >> wrote:
> >>
> >> Just resolved SOLR-14590.
> >>
> >> On Mon, Jul 6, 2020 at 4:22 AM Ishan Chattopadhyaya 
> >> <[email protected]> wrote:
> >>>
> >>> I'll take a look today, Bruno. Thanks.
> >>>
> >>> On Mon, 6 Jul, 2020, 4:32 pm Bruno Roustant, <[email protected]> 
> >>> wrote:
> >>>>
> >>>> Hi all,
> >>>>
> >>>> 8.6 RC is planned tomorrow but there are still 9 Jira issues unresolved 
> >>>> for 8.6 (+ private ones?)
> >>>>
> >>>> Please review and update their status.
> >>>>
> >>>> 3 blockers
> >>>> SOLR-14599 Introduce cluster level plugins through packages
> >>>> SOLR-14593 Package store API to disable file upload over HTTP
> >>>> SOLR-14580 CloudSolrClient cannot be initialized using 'zkHosts' builder
> >>>>
> >>>> Other
> >>>> SOLR-14590 Add support for FeatureField in Solr
> >>>> SOLR-14516 NPE during Realtime GET
> >>>> SOLR-14422 Solr 8.5 Admin UI shows Angular placeholders on first load / 
> >>>> refresh
> >>>> SOLR-14398 package store PUT should be idempotent
> >>>> SOLR-14311 Shared schema should not have access to core level classes
> >>>> LUCENE-9356 Add tests for corruptions caused by byte flips
> >>>>
> >>>> Le dim. 5 juil. 2020 à 08:10, David Smiley <[email protected]> a 
> >>>> écrit :
> >>>>>
> >>>>> Pertaining to the highlighter performance regression: 
> >>>>> https://issues.apache.org/jira/browse/SOLR-14628
> >>>>> It's a simple change in a default setting, that is furthermore 
> >>>>> consistent with how the behavior was prior to Solr 8.5
> >>>>>
> >>>>> I'm hoping this can make it into the release?  See the PR.
> >>>>>
> >>>>> ~ David
> >>>>>
> >>>>>
> >>>>> On Wed, Jun 24, 2020 at 3:05 PM David Smiley <[email protected]> 
> >>>>> wrote:
> >>>>>>
> >>>>>> 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 
> >>>>>> <[email protected]> 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 
> >>>>>>> <[email protected]>, wrote:
> >>>>>>>
> >>>>>>> +1. Thanks Bruno
> >>>>>>>
> >>>>>>> On Wed, Jun 17, 2020 at 6:22 AM Mike Drob <[email protected]> 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 
> >>>>>>>> <[email protected]> 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
> >>
> >>
> >> _______________________
> >> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
> >> http://www.opensourceconnections.com | My Free/Busy
> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed
> >> This e-mail and all contents, including attachments, is considered to be 
> >> Company Confidential unless explicitly stated otherwise, regardless of 
> >> whether attachments are marked as such.
> >>
>
>
> --
> -----------------------------------------------------
> Noble Paul



-- 
-----------------------------------------------------
Noble Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to