Hello Daniel,

We have 3.0.0-beta3 available for testing. It would be helpful if you could
confirm your uses cases work with this version.

Gary


On Mon, Mar 17, 2025, 10:20 Daniel Burrell <daniel.burr...@b2c2.com.invalid>
wrote:

> Dear Apache Logging team,
>
>
> Is a maintainer available to cut this 3.0.0 release? I believe a vote has
> to be called?
>
> 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.
>
> Kind regards,
>
> Daniel Burrell
>
>
> On Tue, Feb 25, 2025 at 4:37 PM Daniel Burrell <daniel.burr...@b2c2.com>
> wrote:
>
> > Hi logging team,
> >
> > Perhaps if there are no further concerns, would it be possible for one of
> > the maintainers to please cut a release of log4j 3.0?
> >
> > Kind regards
> >
> > Daniel Burrell
> >
> >
> > On Wed, 29 Jan 2025 at 23:35, Daniel Burrell <daniel.burr...@b2c2.com>
> > wrote:
> >
> >> Dear Apache Logging team,
> >>
> >>
> >> We've been testing log4j beta3 with much success and appreciate the
> clear
> >> migration documentation, as well as support from ppkarwasz (thank you!).
> >>
> >>
> >> Could you provide any information about the expected timeline for the
> >> release of log4j 3.0.0 GA?
> >>
> >>
> >> Is this something we will see released in the near future or are there
> >> still outstanding issues preventing the release?
> >>
> >>
> >> Thank you for your continued work on this valuable project.
> >>
> >>
> >> Kind regards,
> >>
> >>
> >> Daniel Burrell
> >>
> >
>
> --
>
> Daniel Burrell
>
> Head of Platform Engineering | B2C2 Ltd.
>
> +44 7894 66 80 61 | daniel.burr...@b2c2.com
>
> Digital asset pioneer building the ecosystem of the future
>
> e-FX Awards 2022: Best liquidity provider for crypto derivatives
>
> --
> *This email and any files transmitted with it are confidential and
> intended
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee you must not disseminate, distribute or
> copy this e-mail. Please notify us on regulat...@b2c2.net
> <mailto:regulat...@b2c2.net> immediately if you have received this e-mail
> by mistake and delete this e-mail from your system. If you are not the
> intended recipient you are notified that disclosing, copying, distributing
> or taking any action in reliance on the contents of this information is
> strictly prohibited.*
>

Reply via email to