Hi Piotr,
Thank you for explaining your priorities for upcoming releases and setting
expectations, this is very helpful 😀
Gary
On Tue, Mar 25, 2025, 06:37 Piotr P. Karwasz
wrote:
> Hi Daniel,
>
> On 17.03.2025 15:19, Daniel Burrell wrote:
> > Is a maintainer available to cut this 3.0.0 release? I believe a vote has
> > to be called?
>
> Since January no maintainer can contribute to Log4j as part of their
> dayjob, so the development of Log4j has been processing at an extremely
> slow pace. Optimistically we can dedicate maybe 8 hours a week to the
> project counting all maintainers. This time is often spent on answering
> issue reports, but we are working on a way to make the queue of our
> maintainer tasks and especially their order more transparent.
>
> Personally my priorities right now are:
>
> 1. Release Log4j Transform 0.3.0, which has a converter between
> configuration formats that I think will be the most useful to users.
>
> 2. Release Log4j 2.25.0, which is 3 months overdue and often requested
> by GraalVM users.
>
> 3. Port changes introduced in 2.25.0 to 3.x: there is a long list of
> features and fixes that we didn't have time to add to 3.x[1]. GraalVM
> support is probably the biggest one[2] and is required to pass our
> integration tests.
>
>
> So realistically, I don't think a release of 3.x will happen before the
> end of April.
>
> [1] https://github.com/apache/logging-log4j2/issues/3161
>
> [2] https://github.com/apache/logging-log4j2/issues/3055
>
> > I would refer to the discussion thread where I raised this originally in
> > December, but this has been disabled on github repo for some reason.
>
> Discussions disappeared due to a major upgrade of the tools used by
> Apache INFRA. INFRA informed us of this possibility and we reenabled
> Discussions.
>
> Piotr
>
>
