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 flu
Hi Ralph,
On Sun, 4 Jun 2023 at 05:28, Ralph Goers 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
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.
Ra
FWIW, I am noticing that not all the new modules are listed under the
Components section. Do they need to be?
Ralph
> On Jun 3, 2023, at 5:18 PM, Ralph Goers wrote:
>
> In preparation for releasing Log4j 3.0.0-alpha1 in the near future I have
> published the web site to https://logging.staged
In preparation for releasing Log4j 3.0.0-alpha1 in the near future I have
published the web site to https://logging.staged.apache.org/log4j/3.x/. Please
review the web site and make changes where appropriate.
Ralph
