This is the general process I follow when it is time for a release: 1. Look through the outstanding PRs and determine if there are any I can easily address. 2. Look through the Jira issues and determine if there are any that are very serious or are very easy to remedy. 3. After working through these (which usually takes a few days) I then run the build and site build to ensure there are no problems. 4. I then create the release notes, poms, and other files in preparation for the release. 5. I run the release build - typically takes an hour. 6. I run the site build and publish to the staging site. 7. I copy the distribution artifacts to the ASF dev download location. 8. I prepare the email for the release vote 9. Wait 3 days for the vote to complete. If a problem is found the current release vote will be cancelled, the problem corrected, and then steps 5 through 8 are done again. 10. Once the release vote happens the artifacts are released from the ASFs Nexus repository to Maven Central, the web site is published, and the artifacts are made available to the Log4j downloads page.
So this usually takes from 5 to 7 days before the release is available. Ralph > On Aug 29, 2022, at 11:39 AM, Boris Unckel <bu.apa...@mail.unckel.net> wrote: > > Hello Piotr, > >> Piotr P. Karwasz <piotr.karw...@gmail.com> hat am 29.08.2022 20:03 CEST >> geschrieben: >> The next release (2.19.0) will require updating our Log4j2 -> SLF4J >> and SLF4J -> Log4j2 bridges to SLF4J 2.0. If that is also a blocker >> for Wildfly we'll probably manage to release 2.19.0 before your next >> Wildfly version. > > There is a public schedule for WildFly announced[1], all logging belongs to > _WF Core_: > > 27.0.0.Beta1: > > WF Core feature freeze -- Friday Sep 9 > WF feature freeze -- Monday Sep 12 > Tag and release -- Wednesday Sep 14 / Thur Sep 15 > > 27.0.0.Final: > > WF Core feature freeze -- Friday Sep 23 > WF feature freeze -- Monday Sep 26 > Tag and release -- Wednesday Sep 28 / Thur Sep 29 > > I assume the update of SLF4J 2.0 and log4j 2.19.0 will be considered as "big" > change for the logging subsystem and must be available in the beta. I'm going > to prepare a PR for the relevant JBoss Logging dependencies, let's see what > James can do. > > Regards > Boris > > [1] > https://lists.jboss.org/archives/list/wildfly-...@lists.jboss.org/thread/UMOETDN6NSQ4ATAUVSBFHGSCIXQOZDAJ/
