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 th
Hello Piotr,
> Piotr P. Karwasz 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
Hi Boris,
On Tue, 23 Aug 2022 at 09:37, Boris Unckel wrote:
> LOG4J2-3579 is as blocker to integrate 2.18.0 in WildFly, would it be
> possible to release 2.18.1 soon? Could you provide a tag for 2.18.1 in git,
> please? 2.18.0 has only be released to Maven Central, without tag.
The release pro
