Thanks for being so structured and transparent about your proposals, David. 
I'll not comment on each JIRA here but reply to your "approval" question.

As RM my primary concern is to see to that the release happens, in due time, 
with good quality and with no last-minute changes that causes instability.
I do NOT have a need to display authority as RM, by pretending to know better 
than anyone else what is best for the project.
So I'll likely respect any consensus from the committer's meeting next week wrt 
JIRAs to add as blockers for 9.0.

I'm pleased to see the momentum on wrapping things up, this is exactly how 
preparing for a major release in a healthy project should be.
We all now realize that we have to let go of some hopes we had for 9.0. Still, 
many impactful changes are still within reach if they are not too intrusive.
I think starting a new thread here on dev@ for each proposal has worked really 
well so far. Perhaps tag the subject with [9.0 PROPOSAL] ?

Wrt branches, let's utilize the main -> branch_9x -> if(blocker) { branch_9_0 } 
workflow.
It is much easier to advocate for a blocker if it has baked in main for a week 
or two!

Jan


> 14. jan. 2022 kl. 05:47 skrev David Smiley <[email protected]>:
> 
> The following changes are on my mind for 9.0, and some others.  I will do 
> many; others I'm a reviewer for a contributor. I think these are best done on 
> a major release, but this isn't to say each is "important".  Jan (as RM), 
> please let me know what you think.  I suppose I need your approval?
> 
> Observability:
> * https://issues.apache.org/jira/browse/SOLR-14686 
> <https://issues.apache.org/jira/browse/SOLR-14686> Remove log "[coreName]" 
> (logid) which is redundant with MDC
> -- PR just updated and tagged some possible reviewers.  No feedback yet :-/  
> I'll merge soon.
> * https://issues.apache.org/jira/browse/SOLR-15905 
> <https://issues.apache.org/jira/browse/SOLR-15905> "Don't automatically 
> register Solr's metrics with JMX (SolrJmxReporter)"
> -- Yet our default solr.xml could keep it?.  ETA Jan 24
> * https://issues.apache.org/jira/browse/SOLR-14401 
> <https://issues.apache.org/jira/browse/SOLR-14401> ""distrib" request handler 
> metrics should only be tracked on pertinent handlers"
> -- Looking for some feedback on the issue first.  ETA Jan 24
> 
> Highlighting:
> * https://issues.apache.org/jira/browse/SOLR-15259 
> <https://issues.apache.org/jira/browse/SOLR-15259> lower default 
> hl.fragAlignRatio
> -- minor change but better to change highlighting fragment defaults in a 
> major release but not critical.  ETA: Jan 17
> * https://issues.apache.org/jira/browse/SOLR-12901 
> <https://issues.apache.org/jira/browse/SOLR-12901> Make UnifiedHighlighter 
> the default
> -- There are some overlaps between the highlighters but I definitely think 
> the UH is the best highlighter.  ETA Jan 21
> -- separate issue, TBD: removing the big/verbose configs for the other 
> highlighters from the default solrconfig.xml to keep it leaner. 
> 
> Docker:
> * JIRA TBD, Java 17 runtime.  ETA Jan 17
> 
> Filter.java; remove/hide
> * https://issues.apache.org/jira/browse/SOLR-12336 
> <https://issues.apache.org/jira/browse/SOLR-12336> "Remove Filter from Solr"
> -- a contributor has something but is getting approval.  If we don't get this 
> in time, I could do something simple to just ensure the class isn't public.
> 
> Nested Docs:
> * https://issues.apache.org/jira/browse/SOLR-15064 
> <https://issues.apache.org/jira/browse/SOLR-15064> "Atomic/partial updates to 
> nested docs should not assume _route_ param is the root ID" 
> -- Debt/confusion to be removed. ETA 21 Jan
> 
> Modularizing:
> * Solrj-Zookeeper: ETA Jan 17
> * https://issues.apache.org/jira/browse/SOLR-14660 
> <https://issues.apache.org/jira/browse/SOLR-14660>  HDFS (or Hadoop?)
> -- Waiting for the contributor to return to it.  See the issue for discussion 
> on what to do if it stagnates further.
> 
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley 
> <http://www.linkedin.com/in/davidwsmiley>

Reply via email to