[Discuss][VOTE] Release Apache Log4j `2.24.0`
I looked at the download page and it does NOT meet the requirements for a release announcement: "Announcements must contain a link to the relevant download page for the source.” The download page contains a link to a generic directory listing of all Logging Services releases. You can quibble here about whether what is being done meets the requirements, but it doesn’t matter. All announcements get moderated and Sebb will check this and if he doesn’t like it he will reject the announcement email. Note that the web site is NOT officially part of the release so I am NOT going to vote -1 due to any web site issues. Just be aware you are likely to have problems announcing the release. Ralph > On Aug 31, 2024, at 12:30 PM, Piotr P. Karwasz > wrote: > > This is a vote to release the Apache Log4j `2.24.0`. > > Website: https://logging.staged.apache.org/log4j/2.24.0/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: 08053687456f6be61ee8206da782a3d051928a57 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1293 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 72 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > == Review kit > > The minimum set of steps needed to review the uploaded distribution > files in the Subversion repository can be summarized as follows: > ># Check out the distribution >svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 && cd $_ > ># Verify checksums >shasum --check *.sha512 > ># Verify signatures >wget -O - https://downloads.apache.org/logging/KEYS | gpg --import >for sigFile in *.asc; do gpg --verify $sigFile; done > ># Verify reproduciblity >umask 0022 >unzip *-src.zip -d src >cd src >export > NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1293 >sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO ># If preferred, augment `mvnw` with `-DskipTests` to speed things up > > == Release Notes > > This release contains improvements and changes in several areas of Apache > Log4j: > > === Log4j API > > The `2.24.0` version of Log4j API has been enhanced with changes from > the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core > releases. > The changes include: > > * A faster default `ThreadContextMap`. > * Enhanced GraalVM support: native binaries that use Log4j API will no > longer require additional GraalVM configuration. > * The configuration properties subsystem now only accepts the official > pre-2.10 property names and the normalized post-2.10 names. > Check your configuration for typos. > > === Documentation > > The Apache Log4j 2 website has been almost entirely rewritten to > provide improved documentation and faster access to the information > you need. > > [1] https://logging.staged.apache.org/log4j/2.24.0/index.html > > === Bridges > > The JUL-to-Log4j API and Log4j 1-to-Log4j API will no longer be able > to modify the configuration of Log4j Core by default. > If such a functionality is required, it must be explicitly enabled. > > === Modules > > The following Log4j Core additional modules have been removed: > > `log4j-flume-ng`:: > The module has been moved to the Flume project and follows the Apache > Flume release lifecycle. > > `log4j-kubernetes`:: > The module has been moved to the > https://github.com/fabric8io/kubernetes-client/blob/main/doc/KubernetesLog4j.md[Fabric8.io > Kubernetes project] and follows the Fabric8.io release lifecycle. > > `log4j-mongodb3`:: > The module based on MongoDB Java client version 3.x has been removed. > Please migrate to `log4j-mongodb` (client version 5.x) or > `log4j-mongodb4` (client version 4.x). > > === JMX changes > > Starting in version 2.24.0, JMX support is disabled by default and can > be re-enabled via the `log4j2.disableJmx=false` system property. > > === Added > > * Add a faster `DefaultThreadContextMap` implementation. (#2330) > * Add Logback throwable-consuming semantics as an option in > `log4j-slf4j-impl` and `log4j-slf4j2-impl`. Users can enable it by > setting the property `log4j2.messageFactory` to > `org.apache.logging.slf4j.message.ThrowableConsumingMessageFactory`. > (#2363) > * Add trace context fields to `GcpLayout.json` (#2498) > * Add _"Plugin Reference"_ to the website. It is a Javadoc-on-steroids > focusing on Log4j plugins. (#1954) > * Automate website deployment using the new CI infrastructure shipped > with `org.apache.loggin
Re: [Discuss][VOTE] Release Apache Log4j `2.24.0`
No. ScopedContext would have been new in 2.24.0. Piotr didn’t wanted it included in 2.24.0 as we agreed that all the private crap for the ThreadContext and ScopedContext and other Context related stuff should be moved to a new module. In the meantime he was to move the private ThreadContext stuff into Log4j-core. I haven’t actually checked the release yet but I am assuming that happened. Ralph > On Aug 31, 2024, at 2:21 PM, Gary Gregory wrote: > > I've not looked at details but Ralph's comment hints that we need to > explain to users how to migrate if it's anything more than an import > change. WDYT? > > Gary > > On Sat, Aug 31, 2024, 5:06 PM Ralph Goers > wrote: > >> The API section has >> >> Thread Context is mostly superseded by Scoped Context, which, unlike >> Thread Context, >>• is safe to use in servlet applications >>• can store any Object-typed value >> >> >> While I totally agree with this I was under the impression that >> ScopedContext was removed from Log4j 2.24.0, so this will lead to user >> questions. >> >> Ralph >> >>> On Aug 31, 2024, at 2:00 PM, Ralph Goers >> wrote: >>> >>> The release notes page says: >>> >>> "log4j-flume-ngT >>> The module has been moved to the Flume project and follows the Apache >> Flume release lifecycle. >>> >>> We NEVER discussed this. We simply discussed moving it to another repo. >> As in 3.0.0, where more modules are split out, I believe it would be more >> appropriate to say that they will have their own release cycles. >>> >>> Ralph >>> On Aug 31, 2024, at 1:55 PM, Ralph Goers >> wrote: I looked at the download page and it does NOT meet the requirements for >> a release announcement: "Announcements must contain a link to the relevant download page for >> the source.” The download page contains a link to a generic directory >> listing of all Logging Services releases. You can quibble here about whether what is being done meets the >> requirements, but it doesn’t matter. All announcements get moderated and >> Sebb will check this and if he doesn’t like it he will reject the >> announcement email. Note that the web site is NOT officially part of the release so I am >> NOT going to vote -1 due to any web site issues. Just be aware you are >> likely to have problems announcing the release. Ralph > On Aug 31, 2024, at 12:30 PM, Piotr P. Karwasz < >> piotr.karw...@gmail.com> wrote: > > This is a vote to release the Apache Log4j `2.24.0`. > > Website: https://logging.staged.apache.org/log4j/2.24.0/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: 08053687456f6be61ee8206da782a3d051928a57 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j > Nexus: >> https://repository.apache.org/content/repositories/orgapachelogging-1293 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 72 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > == Review kit > > The minimum set of steps needed to review the uploaded distribution > files in the Subversion repository can be summarized as follows: > > # Check out the distribution > svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 >> && cd $_ > > # Verify checksums > shasum --check *.sha512 > > # Verify signatures > wget -O - https://downloads.apache.org/logging/KEYS | gpg --import > for sigFile in *.asc; do gpg --verify $sigFile; done > > # Verify reproduciblity > umask 0022 > unzip *-src.zip -d src > cd src > export NEXUS_REPO= >> https://repository.apache.org/content/repositories/orgapachelogging-1293 > sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO > # If preferred, augment `mvnw` with `-DskipTests` to speed things up > > == Release Notes > > This release contains improvements and changes in several areas of >> Apache Log4j: > > === Log4j API > > The `2.24.0` version of Log4j API has been enhanced with changes from > the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core > releases. > The changes include: > > * A faster default `ThreadContextMap`. > * Enhanced GraalVM support: native binaries that use Log4j API will no > longer require additional GraalVM configuration. > * The configuration properties subsystem now only accepts the official > pre-2.10 property names and the normalized post-2.10 na
[VOTE] Release Apache Log4j `2.24.0`
This is a vote to release the Apache Log4j `2.24.0`. Website: https://logging.staged.apache.org/log4j/2.24.0/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: 08053687456f6be61ee8206da782a3d051928a57 Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1293 Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 Please download, test, and cast your votes on this mailing list. [ ] +1, release the artifacts [ ] -1, don't release, because... This vote is open for 72 hours and will pass unless getting a net negative vote count. All votes are welcome and we encourage everyone to test the release, but only the Logging Services PMC votes are officially counted. At least 3 +1 votes and more positive than negative votes are required. == Review kit The minimum set of steps needed to review the uploaded distribution files in the Subversion repository can be summarized as follows: # Check out the distribution svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 && cd $_ # Verify checksums shasum --check *.sha512 # Verify signatures wget -O - https://downloads.apache.org/logging/KEYS | gpg --import for sigFile in *.asc; do gpg --verify $sigFile; done # Verify reproduciblity umask 0022 unzip *-src.zip -d src cd src export NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1293 sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO # If preferred, augment `mvnw` with `-DskipTests` to speed things up == Release Notes This release contains improvements and changes in several areas of Apache Log4j: === Log4j API The `2.24.0` version of Log4j API has been enhanced with changes from the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core releases. The changes include: * A faster default `ThreadContextMap`. * Enhanced GraalVM support: native binaries that use Log4j API will no longer require additional GraalVM configuration. * The configuration properties subsystem now only accepts the official pre-2.10 property names and the normalized post-2.10 names. Check your configuration for typos. === Documentation The Apache Log4j 2 website has been almost entirely rewritten to provide improved documentation and faster access to the information you need. [1] https://logging.staged.apache.org/log4j/2.24.0/index.html === Bridges The JUL-to-Log4j API and Log4j 1-to-Log4j API will no longer be able to modify the configuration of Log4j Core by default. If such a functionality is required, it must be explicitly enabled. === Modules The following Log4j Core additional modules have been removed: `log4j-flume-ng`:: The module has been moved to the Flume project and follows the Apache Flume release lifecycle. `log4j-kubernetes`:: The module has been moved to the https://github.com/fabric8io/kubernetes-client/blob/main/doc/KubernetesLog4j.md[Fabric8.io Kubernetes project] and follows the Fabric8.io release lifecycle. `log4j-mongodb3`:: The module based on MongoDB Java client version 3.x has been removed. Please migrate to `log4j-mongodb` (client version 5.x) or `log4j-mongodb4` (client version 4.x). === JMX changes Starting in version 2.24.0, JMX support is disabled by default and can be re-enabled via the `log4j2.disableJmx=false` system property. === Added * Add a faster `DefaultThreadContextMap` implementation. (#2330) * Add Logback throwable-consuming semantics as an option in `log4j-slf4j-impl` and `log4j-slf4j2-impl`. Users can enable it by setting the property `log4j2.messageFactory` to `org.apache.logging.slf4j.message.ThrowableConsumingMessageFactory`. (#2363) * Add trace context fields to `GcpLayout.json` (#2498) * Add _"Plugin Reference"_ to the website. It is a Javadoc-on-steroids focusing on Log4j plugins. (#1954) * Automate website deployment using the new CI infrastructure shipped with `org.apache.logging:logging-parent:11.0.0` === Changed * Fix usage of `log4j-api` in GraalVM without additional reachability data. (#1539) * Ignore exceptions thrown by PropertySources. (https://github.com/spring-projects/spring-boot/issues/33450[Spring-33450]) * Add logging to `PropertiesUtil` and fix `Duration` parser. (#1936) * Disable level modification via JUL by default. (#2353) * Centralize initialization in the `Provider` class and deprecate `log4j2.loggerContextFactory` property. (#2374) * Remove `log4j-kubernetes` lookup. User should migrate to https://github.com/fabric8io/kubernetes-client/blob/main/doc/KubernetesLog4j.md[`io.fabric8:kubernetes-log4j`]. (#2412) * Disable JMX support by default. Require `log4j2.disableJmx` to be set to `false` to enable JMX support. (#2462) * Replace some usages of `DateTimeFormatter#toString()` with `DateTimeFormatter#formatTo(StringBuilder)` to cut down on allocations (#2515) * Disable programmatic configuration in Log4j 1 Bridge if `log4j1.c
Re: [Discuss][VOTE] Release Apache Log4j `2.24.0`
The release notes page says: "log4j-flume-ngT The module has been moved to the Flume project and follows the Apache Flume release lifecycle. We NEVER discussed this. We simply discussed moving it to another repo. As in 3.0.0, where more modules are split out, I believe it would be more appropriate to say that they will have their own release cycles. Ralph > On Aug 31, 2024, at 1:55 PM, Ralph Goers wrote: > > I looked at the download page and it does NOT meet the requirements for a > release announcement: > "Announcements must contain a link to the relevant download page for the > source.” The download page contains a link to a generic directory listing of > all Logging Services releases. > > You can quibble here about whether what is being done meets the requirements, > but it doesn’t matter. All announcements get moderated and Sebb will check > this and if he doesn’t like it he will reject the announcement email. > > Note that the web site is NOT officially part of the release so I am NOT > going to vote -1 due to any web site issues. Just be aware you are likely to > have problems announcing the release. > > Ralph > > >> On Aug 31, 2024, at 12:30 PM, Piotr P. Karwasz >> wrote: >> >> This is a vote to release the Apache Log4j `2.24.0`. >> >> Website: https://logging.staged.apache.org/log4j/2.24.0/index.html >> GitHub: https://github.com/apache/logging-log4j2 >> Commit: 08053687456f6be61ee8206da782a3d051928a57 >> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j >> Nexus: >> https://repository.apache.org/content/repositories/orgapachelogging-1293 >> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 >> >> Please download, test, and cast your votes on this mailing list. >> >> [ ] +1, release the artifacts >> [ ] -1, don't release, because... >> >> This vote is open for 72 hours and will pass unless getting a >> net negative vote count. All votes are welcome and we encourage >> everyone to test the release, but only the Logging Services PMC >> votes are officially counted. At least 3 +1 votes and more >> positive than negative votes are required. >> >> == Review kit >> >> The minimum set of steps needed to review the uploaded distribution >> files in the Subversion repository can be summarized as follows: >> >> # Check out the distribution >> svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 && cd $_ >> >> # Verify checksums >> shasum --check *.sha512 >> >> # Verify signatures >> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import >> for sigFile in *.asc; do gpg --verify $sigFile; done >> >> # Verify reproduciblity >> umask 0022 >> unzip *-src.zip -d src >> cd src >> export >> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1293 >> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO >> # If preferred, augment `mvnw` with `-DskipTests` to speed things up >> >> == Release Notes >> >> This release contains improvements and changes in several areas of Apache >> Log4j: >> >> === Log4j API >> >> The `2.24.0` version of Log4j API has been enhanced with changes from >> the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core >> releases. >> The changes include: >> >> * A faster default `ThreadContextMap`. >> * Enhanced GraalVM support: native binaries that use Log4j API will no >> longer require additional GraalVM configuration. >> * The configuration properties subsystem now only accepts the official >> pre-2.10 property names and the normalized post-2.10 names. >> Check your configuration for typos. >> >> === Documentation >> >> The Apache Log4j 2 website has been almost entirely rewritten to >> provide improved documentation and faster access to the information >> you need. >> >> [1] https://logging.staged.apache.org/log4j/2.24.0/index.html >> >> === Bridges >> >> The JUL-to-Log4j API and Log4j 1-to-Log4j API will no longer be able >> to modify the configuration of Log4j Core by default. >> If such a functionality is required, it must be explicitly enabled. >> >> === Modules >> >> The following Log4j Core additional modules have been removed: >> >> `log4j-flume-ng`:: >> The module has been moved to the Flume project and follows the Apache >> Flume release lifecycle. >> >> `log4j-kubernetes`:: >> The module has been moved to the >> https://github.com/fabric8io/kubernetes-client/blob/main/doc/KubernetesLog4j.md[Fabric8.io >> Kubernetes project] and follows the Fabric8.io release lifecycle. >> >> `log4j-mongodb3`:: >> The module based on MongoDB Java client version 3.x has been removed. >> Please migrate to `log4j-mongodb` (client version 5.x) or >> `log4j-mongodb4` (client version 4.x). >> >> === JMX changes >> >> Starting in version 2.24.0, JMX support is disabled by default and can >> be re-enabled via the `log4j2.disableJmx=false` system property. >> >> === Added >> >> * Add a faster `DefaultThreadContextM
Re: [Discuss][VOTE] Release Apache Log4j `2.24.0`
I've not looked at details but Ralph's comment hints that we need to explain to users how to migrate if it's anything more than an import change. WDYT? Gary On Sat, Aug 31, 2024, 5:06 PM Ralph Goers wrote: > The API section has > > Thread Context is mostly superseded by Scoped Context, which, unlike > Thread Context, > • is safe to use in servlet applications > • can store any Object-typed value > > > While I totally agree with this I was under the impression that > ScopedContext was removed from Log4j 2.24.0, so this will lead to user > questions. > > Ralph > > > On Aug 31, 2024, at 2:00 PM, Ralph Goers > wrote: > > > > The release notes page says: > > > > "log4j-flume-ngT > > The module has been moved to the Flume project and follows the Apache > Flume release lifecycle. > > > > We NEVER discussed this. We simply discussed moving it to another repo. > As in 3.0.0, where more modules are split out, I believe it would be more > appropriate to say that they will have their own release cycles. > > > > Ralph > > > >> On Aug 31, 2024, at 1:55 PM, Ralph Goers > wrote: > >> > >> I looked at the download page and it does NOT meet the requirements for > a release announcement: > >> "Announcements must contain a link to the relevant download page for > the source.” The download page contains a link to a generic directory > listing of all Logging Services releases. > >> > >> You can quibble here about whether what is being done meets the > requirements, but it doesn’t matter. All announcements get moderated and > Sebb will check this and if he doesn’t like it he will reject the > announcement email. > >> > >> Note that the web site is NOT officially part of the release so I am > NOT going to vote -1 due to any web site issues. Just be aware you are > likely to have problems announcing the release. > >> > >> Ralph > >> > >> > >>> On Aug 31, 2024, at 12:30 PM, Piotr P. Karwasz < > piotr.karw...@gmail.com> wrote: > >>> > >>> This is a vote to release the Apache Log4j `2.24.0`. > >>> > >>> Website: https://logging.staged.apache.org/log4j/2.24.0/index.html > >>> GitHub: https://github.com/apache/logging-log4j2 > >>> Commit: 08053687456f6be61ee8206da782a3d051928a57 > >>> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j > >>> Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1293 > >>> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > >>> > >>> Please download, test, and cast your votes on this mailing list. > >>> > >>> [ ] +1, release the artifacts > >>> [ ] -1, don't release, because... > >>> > >>> This vote is open for 72 hours and will pass unless getting a > >>> net negative vote count. All votes are welcome and we encourage > >>> everyone to test the release, but only the Logging Services PMC > >>> votes are officially counted. At least 3 +1 votes and more > >>> positive than negative votes are required. > >>> > >>> == Review kit > >>> > >>> The minimum set of steps needed to review the uploaded distribution > >>> files in the Subversion repository can be summarized as follows: > >>> > >>> # Check out the distribution > >>> svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 > && cd $_ > >>> > >>> # Verify checksums > >>> shasum --check *.sha512 > >>> > >>> # Verify signatures > >>> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import > >>> for sigFile in *.asc; do gpg --verify $sigFile; done > >>> > >>> # Verify reproduciblity > >>> umask 0022 > >>> unzip *-src.zip -d src > >>> cd src > >>> export NEXUS_REPO= > https://repository.apache.org/content/repositories/orgapachelogging-1293 > >>> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO > >>> # If preferred, augment `mvnw` with `-DskipTests` to speed things up > >>> > >>> == Release Notes > >>> > >>> This release contains improvements and changes in several areas of > Apache Log4j: > >>> > >>> === Log4j API > >>> > >>> The `2.24.0` version of Log4j API has been enhanced with changes from > >>> the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core > >>> releases. > >>> The changes include: > >>> > >>> * A faster default `ThreadContextMap`. > >>> * Enhanced GraalVM support: native binaries that use Log4j API will no > >>> longer require additional GraalVM configuration. > >>> * The configuration properties subsystem now only accepts the official > >>> pre-2.10 property names and the normalized post-2.10 names. > >>> Check your configuration for typos. > >>> > >>> === Documentation > >>> > >>> The Apache Log4j 2 website has been almost entirely rewritten to > >>> provide improved documentation and faster access to the information > >>> you need. > >>> > >>> [1] https://logging.staged.apache.org/log4j/2.24.0/index.html > >>> > >>> === Bridges > >>> > >>> The JUL-to-Log4j API and Log4j 1-to-Log4j API will no longer be able > >>> to modify the configuration of Log4j Core by default. > >>> If such a functionality is required,
Re: [Discuss][VOTE] Release Apache Log4j `2.24.0`
The API section has Thread Context is mostly superseded by Scoped Context, which, unlike Thread Context, • is safe to use in servlet applications • can store any Object-typed value While I totally agree with this I was under the impression that ScopedContext was removed from Log4j 2.24.0, so this will lead to user questions. Ralph > On Aug 31, 2024, at 2:00 PM, Ralph Goers wrote: > > The release notes page says: > > "log4j-flume-ngT > The module has been moved to the Flume project and follows the Apache Flume > release lifecycle. > > We NEVER discussed this. We simply discussed moving it to another repo. As in > 3.0.0, where more modules are split out, I believe it would be more > appropriate to say that they will have their own release cycles. > > Ralph > >> On Aug 31, 2024, at 1:55 PM, Ralph Goers wrote: >> >> I looked at the download page and it does NOT meet the requirements for a >> release announcement: >> "Announcements must contain a link to the relevant download page for the >> source.” The download page contains a link to a generic directory listing >> of all Logging Services releases. >> >> You can quibble here about whether what is being done meets the >> requirements, but it doesn’t matter. All announcements get moderated and >> Sebb will check this and if he doesn’t like it he will reject the >> announcement email. >> >> Note that the web site is NOT officially part of the release so I am NOT >> going to vote -1 due to any web site issues. Just be aware you are likely to >> have problems announcing the release. >> >> Ralph >> >> >>> On Aug 31, 2024, at 12:30 PM, Piotr P. Karwasz >>> wrote: >>> >>> This is a vote to release the Apache Log4j `2.24.0`. >>> >>> Website: https://logging.staged.apache.org/log4j/2.24.0/index.html >>> GitHub: https://github.com/apache/logging-log4j2 >>> Commit: 08053687456f6be61ee8206da782a3d051928a57 >>> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j >>> Nexus: >>> https://repository.apache.org/content/repositories/orgapachelogging-1293 >>> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 >>> >>> Please download, test, and cast your votes on this mailing list. >>> >>> [ ] +1, release the artifacts >>> [ ] -1, don't release, because... >>> >>> This vote is open for 72 hours and will pass unless getting a >>> net negative vote count. All votes are welcome and we encourage >>> everyone to test the release, but only the Logging Services PMC >>> votes are officially counted. At least 3 +1 votes and more >>> positive than negative votes are required. >>> >>> == Review kit >>> >>> The minimum set of steps needed to review the uploaded distribution >>> files in the Subversion repository can be summarized as follows: >>> >>> # Check out the distribution >>> svn co https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.0 && cd $_ >>> >>> # Verify checksums >>> shasum --check *.sha512 >>> >>> # Verify signatures >>> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import >>> for sigFile in *.asc; do gpg --verify $sigFile; done >>> >>> # Verify reproduciblity >>> umask 0022 >>> unzip *-src.zip -d src >>> cd src >>> export >>> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1293 >>> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO >>> # If preferred, augment `mvnw` with `-DskipTests` to speed things up >>> >>> == Release Notes >>> >>> This release contains improvements and changes in several areas of Apache >>> Log4j: >>> >>> === Log4j API >>> >>> The `2.24.0` version of Log4j API has been enhanced with changes from >>> the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core >>> releases. >>> The changes include: >>> >>> * A faster default `ThreadContextMap`. >>> * Enhanced GraalVM support: native binaries that use Log4j API will no >>> longer require additional GraalVM configuration. >>> * The configuration properties subsystem now only accepts the official >>> pre-2.10 property names and the normalized post-2.10 names. >>> Check your configuration for typos. >>> >>> === Documentation >>> >>> The Apache Log4j 2 website has been almost entirely rewritten to >>> provide improved documentation and faster access to the information >>> you need. >>> >>> [1] https://logging.staged.apache.org/log4j/2.24.0/index.html >>> >>> === Bridges >>> >>> The JUL-to-Log4j API and Log4j 1-to-Log4j API will no longer be able >>> to modify the configuration of Log4j Core by default. >>> If such a functionality is required, it must be explicitly enabled. >>> >>> === Modules >>> >>> The following Log4j Core additional modules have been removed: >>> >>> `log4j-flume-ng`:: >>> The module has been moved to the Flume project and follows the Apache >>> Flume release lifecycle. >>> >>> `log4j-kubernetes`:: >>> The module has been moved to the >>> https://github.com/fabric8io/kubernetes-client/blob/main/doc/KubernetesL
