ppkarwasz commented on issue #3849: URL: https://github.com/apache/logging-log4j2/issues/3849#issuecomment-3102127621
Hi @nagkumar, > > Since there are no plans for a 3.x release of log4j-iostreams, > > I observed there is a version 3.0.0-beta2.. would that be deprecated for use..? Yes, we did publish `log4j-iostreams:3.0.0-beta2`. However, it was released **before** a major architectural shift we made in January 2024, when we decided to **rebase Log4j Core 3.x onto the 2.x API** (see [vote thread](https://lists.apache.org/thread/p2lgr3xtt9hq77j7r67r8x1tc1z7kbol)) to stress out that Log4j Core 3.x does not bring **any** breaking changes to Log4j API users. By the time `3.0.0-beta2` was released, this change hadn’t yet taken effect. Since then, the release strategy for 3.x changed significantly: * Starting with `3.0.0-beta3`, only `log4j-core` and its extensions are published in the 3.x line. * Modules like `log4j-api` and `log4j-iostreams` remain on the 2.x line — intentionally — and are fully compatible with Core 3.x. Because these are all **beta** versions and never intended for production, we haven’t formally deprecated earlier artifacts like `beta2`. That said, you're absolutely right that we should better document this. We’ll look into clarifying that: * **All artifacts from the 3.x line prior to `3.0.0-beta3` are unsupported**. * Only `3.0.0-beta3` and beyond reflect the intended long-term structure and compatibility model. * `beta2` and earlier should be considered obsolete and discouraged for any use. ### Regarding the final `3.0.0` release We're holding off on a final `3.0.0` release not because of critical blockers, but to ensure it's on par with our latest 2.x line. Two main items are pending: * Backporting **GraalVM support**, introduced in Log4j Core 2.25.0 * Finishing the port of various **2.x bug fixes** to 3.x (see #3161) These aren’t blocking issues per se — but we’re aiming for a solid, production-worthy 3.0.0 release. If users like you are testing and ready to adopt Core 3.x in production, we’re happy to postpone those issues and deliver `3.0.0` earlier. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
