GitHub user vy added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release?
@daniel-b2c2, we – @garydgregory, @rgoers, @ppkarwasz, and myself – had a call regarding this subject yesterday and decided to proceed with `3.0.0` GA as it is, and as soon as possible. Let me elaborate on that... > One thing I’ve been wondering: with ongoing work continuing on 2.x and new > changes still needing to be ported over, is there a point where 2.x > development is expected to wind down? From the outside it sometimes feels > like 3.x is perpetually catching up with integrations and backports. > > Is there a policy or expectation that changes should land in main before > being accepted into 2.x, or is the current approach intentional? This is a very sharp and accurate observation. I can share _my explanation_ for that inquiry: 1. @ppkarwasz and I, the only active maintainers since last couple of years, have been extremely busy with Log4j 2, day jobs, and private life. When maintenance tasks are ordered by decreasing priority, the release of Log4j 3 almost always showed at the bottom. There were and are still no incentives in the horizon to change that. 2. @ppkarwasz and I – but mostly @ppkarwasz – put great deal of effort into making the `3.x` branch release ready in 2024 thanks to the STF grant. Yet it is an 8 year old branch, hardly synchronized with `2.x`, if ever, and contains massive changes. 3. At this stage, we have concerns regarding the DI system in `3.x`, there are several issues waiting to be ported (#3161), and the website content is worse than in `2.x`, which is extra problematic given there are significant architectural changes. Plus, we are all extremely exhausted. I guess we will just release `3.0.0` (in a month or two?) and cross our fingers. Yes, ideally only fixes should land on `2.x` and `main`/`3.x` should become the development branch. But I guess now you understand why it isn't. GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-15061535 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
