I’m still working on the updated DI system in a branch, but it’s not a _must have_ for the first alpha. As we did with 2.0, I expect that various levels of API stability (besides log4j-api) won’t be guaranteed until we hit the release candidate phase for 3.0.0. Since the DI stuff is still in flux, I expect that to change a bit over subsequent releases, but that’s not a blocker to getting a first alpha.
> On Jun 3, 2023, at 10:28 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > I believe I have finished the work necessary to successfully perform a > release of Log4j 3.x. I am not aware of any items that MUST be done for a > 3.0.0-alpha1 release. If any of you are please let me know. I will wait a few > days for feedback on this to give you all a chance to review things. > > Ralph
