[
https://issues.apache.org/jira/browse/LOG4J2-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916508#comment-17916508
]
Philippe Cloutier commented on LOG4J2-3695:
-------------------------------------------
Thank you [~pkarwasz]
I checked that ticket and commented; I don't think there will be a migration
path allowing such a move to work, but if there is, it will require a
[semi-]automatic transfer of tickets to GitHub. In any case, I for one will not
manually transfer "my" reports there.
> Release Notes table of contents is partial (first level only)
> -------------------------------------------------------------
>
> Key: LOG4J2-3695
> URL: https://issues.apache.org/jira/browse/LOG4J2-3695
> Project: Log4j 2
> Issue Type: Wish
> Components: Documentation
> Reporter: Philippe Cloutier
> Priority: Trivial
>
> The new [Release
> Notes|https://logging.apache.org/log4j/2.x/release-notes.html] page is very
> long. Thankfully, it contains a ToC to bring to the desired version. However,
> the ToC only shows top-level sections (versions). It would be nice, in
> particular for large sections like 2.24.0, to add a further level, so that
> subsections like Deprecated and Removed are directly available.
> ----
> By the way, there are several misplaced changes, such as:
> # "Remove module log4j-mongodb3, use log4j-mongodb instead, log4j-mongodb4
> is deprecated for removal." in Updated
> # "Removes internal field that leaked into public API." in Added
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
