-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add versioning and support policy information #3341
base: 2.x
Are you sure you want to change the base?
Conversation
This PR adds information about the support status of various Apache Log4j releases. Related to #1867
The classification of behavioral changes as minor or patch release is up to interpretation: what constitutes a bug for one user might be a feature for somebody else. | ||
==== | ||
|
||
=== OSGi package versioning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this subsection collapsible, please?
|
||
Since release `2.21.0` Log4j follows the OSGi practice of versioning each Java package separately (see | ||
https://bnd.bndtools.org/chapters/170-versioning.html#versioning-packages[Versioning Packages] for more information). | ||
The version of each package is available in the manifests of each artifact and in the Javadoc of each package: e.g. the version of the `o.a.l.l.core.appender` package is available in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version of each package is available in the manifests of each artifact and in the Javadoc of each package: e.g. the version of the `o.a.l.l.core.appender` package is available in the | |
The version of each package is available in the manifests of each artifact and in the Javadoc of each package: e.g. the version of the `org.apache.logging.log4j.core.appender` package is available in the |
|
||
== Support policy | ||
|
||
Apache Log4j currently supports two versions: Apache Log4j 2.x and the incubating Apache Log4j Core 3.x as in the table below: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am okay with 2.x
, 3.x
, etc. usages in the table below. Yet, IMHO, we should stick to Log4j 2
, Log4j 3
in the text.
Apache Log4j currently supports two versions: Apache Log4j 2.x and the incubating Apache Log4j Core 3.x as in the table below: | |
Apache Log4j currently supports two versions: Apache Log4j 2 and the incubating Apache Log4j Core 3 as in the table below: |
+ | ||
The version is under active development. | ||
|
||
EOS:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EOS:: | |
End-of-Support (EOS):: |
The version will not receive any updates, including security updates. | ||
New security advisories against this version might be published in the future. | ||
|
||
EOL:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EOL:: | |
End-of-Life (EOL):: |
This PR adds information about the support status of various Apache Log4j releases.
Related to #1867