Hi Ralph, On Thu, 15 Jun 2023 at 22:12, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x > series. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... > > The vote will remain open for 72 hours. All votes are welcome and we > encourage everyone to test the release, but only Logging PMC votes are > “officially” counted. As always, at least 3 +1 votes and more positive than > negative votes are required.
Thank You for breaking the impasse on the 3.x release. Due to the significance of the release, I will cast my vote near the deadline: https://www.timeanddate.com/countdown/birthday?iso=20230618T131145&p0=197&font=cursive One matter that I will not take into account in the vote, but that we should fix before the announcement is the changelog. It contains a lot of entries that were already included in 2.20.0 like these: > Changes in this version include: > (...) > • Update Apache Flume from 1.7.0 to 1.8.0. (for LOG4J2-2082 by Gary > Gregory) > • Update Eclipse javax.persistence from 2.1.1 to 2.2.0. (for LOG4J2-2083 > by Gary Gregory) > • Update build to expect Java 8 sources and generate Java 8 byte codes. > (for LOG4J2-2083 by Gary Gregory) > (...) > • Update Apache Flume from 1.8.0 to 1.9.0. (for LOG4J2-2572 by Gary > Gregory) Users will probably read these carefully and such entries are misleading. I can probably sort them out by the end of the voting period, so that we can update the website shortly thereafter. BTW the introduction to the release notes says "Changes staged for the next 3.x.x version that is yet to be released". Piotr
