Normally I take care of that, though anyone on the PMC can do it. It’s a normal `mvn release:prepare release:publish` along with logging in yo repository.apache.org to close the release and prepare as a release candidate. Instructions are all on our Confluence page about it.
— Matt Sicker > On Sep 18, 2022, at 07:49, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Ralph, > >> On Sun, 18 Sept 2022 at 01:30, Ralph Goers <ralph.go...@dslextreme.com> >> wrote: >> I would suggest that if you bump the logging parent to use it and then test >> Log4j >> with it and get a successful build then just do it. We don’t need to discuss >> stuff like >> this if it works. > > The upgrade required adding a couple of automatic module names to > artifacts that didn't have them. > Otherwise it passes the tests (also `./mvnw site`): > https://github.com/apache/logging-log4j2/pull/1063 > > The builds are finally reproducible (I tested on the `log4j-api` JAR). > > Ralph, could you release `logging-parent` version 6? > > Piotr
