[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457702#comment-17457702
]
Mike Drob commented on SOLR-15843:
----------------------------------
> We could add something to the solr-upgrade-notes page for 8.11.1 and
> republish the page in the Ref Guide once 8.11.1 is actually out
I considered this, but it feels weird to list something in the upgrade notes
that is "no action required" when upgrading? We need a section for what to do
if you can't upgrade the security page seemed like the best choice. I'm not
opposed to this, and hopefully you can come up with better writing than I
could, but I was unhappy with anything I could produce.
> Update Log4J dependency
> -----------------------
>
> Key: SOLR-15843
> URL: https://issues.apache.org/jira/browse/SOLR-15843
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Critical
> Fix For: 9.0, 8.11.1
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Log4j 2.15 is about to be released, we should update when it is available.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
