As some of you may have noticed already, I’ve been going through the 3.0.0 items in our backlog issue [0], our 3.0.0-beta4 milestone [1], and the 3.x milestone in general [2]. I’ve started with handling many of the parts that could be easily cherry-picked (with minimal merge conflicts to deal with) and have gotten through a good chunk of them.
I’m currently working on the GraalVM reachability metadata issue for 3.x which is not a straightforward cherry-pick due to major enhancements in the plugin system. This will also subsume a 2.x PR related to added warnings on the annotation processor for missing builder methods (in 3.x, the annotation processor would make more sense to emit warnings about non-public members being annotated for plugin usage to help avoid breaking module boundaries and such). Due to the amount of metadata that’s needed to generate for GraalVM, this may enable support for code generation for the DI system at some point (comparable to Spring’s AOT compilation support or frameworks like Quarkus and Helidon), but that can be implemented whenever. There are also changes related to MessageFactory-namespaced logger registries (which required a 2.x release which has already happened), plugin documentation updates (which I mostly handled a while ago with a few tasks remaining), and a couple bugs. Assuming these lists are relatively complete, I imagine we can cut a 3.0.0-beta4 release by the end of this month or during September. Then we can take a last look at APIs to see if there are any breaking changes we want before leaving them in place until 4.0. [0]: https://github.com/apache/logging-log4j2/issues/3161 [1]: https://github.com/apache/logging-log4j2/milestone/19 [2]: https://github.com/apache/logging-log4j2/milestone/2
