ppkarwasz commented on issue #4176: URL: https://github.com/apache/logging-log4j2/issues/4176#issuecomment-4917064618
Hi @muzzle2023, Package versions in Log4j are **not** aligned with the release number. We follow the standard [OSGi versioning scheme](https://bnd.bndtools.org/chapters/170-versioning.html#versions-in-osgi): - The **patch** number increases for changes that are almost irrelevant to the public API (e.g. the value of an annotation). - The **minor** number increases when the public API gets a backward-compatible addition (e.g. a new public method). - The **major** number increases only on a breaking change to the public API, which happens between major versions of Log4j itself. The package version and the Log4j release version only coincide at the moment a package's public API is actually modified (or when we make a mistake :wink:). So a package at version `2.20.4` had a last significant API change in `2.20.0`; everything since then has been internal. In practice this means you can rely on the package version as a lower bound: if your code depends on a package version of `2.20.4`, Log4j version `2.20.0` or higher should work with your code. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
