The Apache Log4j Tools 0.1.0 release is now available for voting.
The 0.1.0 version is the very first release of this relatively old
repository, which is repurposed for `log4j-changelog`, Log4j's
`maven-changes-plugin` successor. This enables us to build the Log4j
website (incl. manual) in less th
Curious:
In the "classic" changelog, we use "add", "fix", and so on, simple enough.
Here, we use the past tense "added", and so on, except that we don't use
"secured", we use "security", an odd inconsistency I guess. Any reason for
that?
FWIW, I like the simpler shorter words "add" and so on.
Ga
The rationale was explained in the `log4j-changelog` README:
https://github.com/apache/logging-log4j-tools/blob/master/log4j-changelog/README.adoc
In a nutshell, we stick to the https://keepachangelog.com/en/1.0.0/
specification.
I share the same grammatical concern, yet, it might be better to sti
Ah, I see, the author of https://keepachangelog.com/en/1.0.0/ is not a
native English speaker, and shares the same French background as I do,
maybe it explains it, regardless, if that's what we want to do, so be it.
Gary
On Tue, Jan 10, 2023, 07:05 Volkan Yazıcı wrote:
> The rationale was expla
Why are we changing to follow a spec we have never used before? I have
concerns about “security” as a type. Unless we are going to support multiple
types this doesn’t make a lot of sense to me as generally these fixes will be
bugs. And rather than have a type of “security” I would prefer that i
Hi Volkan,
On Tue, 10 Jan 2023 at 11:54, Volkan Yazıcı wrote:
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1096
> Signing key:
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0&fingerprint=on&op=index
The hashe
