Hi Ralph, On Mon, 20 Mar 2023 at 15:09, Apache <ralph.go...@dslextreme.com> wrote: > > I would be comfortable with this if it is moved to its own repo and released > first, then removed from the Log4J repo. I am not comfortable with “we can do > it someday if we want to” unless we are dropping support for it.
Can we keep 2.20.0 as current release and release a new version of `log4j-jmx-gui` as soon as we fix some bug in it? `log4j-bom` is also mainly independent from the rest of the modules, so we can move it to a separate repo. A Log4j2 release would technically consist of a release of `l-log4j2` followed by a release of `l-l-bom` that bumps all versions (except `log4j-jmx-gui`). Piotr
