What do you mean? That is exactly the link I shared in the very first
section of the VOTE email you responded to. See the `=== Timing &
Differences` header. Note that you don't need to trust the GitHub view, you
can diff RC2 and RC3 using their commit IDs available in the associated
VOTE emails.

On Thu, Mar 21, 2024 at 5:00 PM Gary Gregory <garydgreg...@gmail.com> wrote:

> What's the difference with RC2?
>
> TY,
> Gary
>
> On Thu, Mar 21, 2024, 11:46 AM Volkan Yazıcı <vol...@yazi.ci> wrote:
>
> > This is a vote to release the Apache Log4j Tools 0.8.0 (RC3).
> >
> > Website: https://logging.staged.apache.org/log4j/tools
> > GitHub: https://github.com/apache/logging-log4j-tools
> > Commit: 7d157b61e198e3baca816129d8d406b300436e2f
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> > Nexus:
> > https://repository.apache.org/content/repositories/orgapachelogging-1266
> > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> >
> > Please download, test, and cast your votes on this mailing list.
> >
> > [ ] +1, release the artifacts
> > [ ] -1, don't release, because...
> >
> > This vote is open until 2024-03-22 12:30 (CET) and will pass unless
> > getting a net negative vote count. All votes are welcome and we
> > encourage everyone to test the release, but only the Logging
> > Services PMC votes are officially counted. At least 3 +1 votes and
> > more positive than negative votes are required.
> >
> > === Timing & Differences
> >
> > I will keep this vote open until 2024-03-22 12:30 (CET), that is, the
> > official end date of the RC2, since RC3 contains a minor difference:
> >
> >
> >
> https://github.com/apache/logging-log4j-tools/compare/2bb07037bbbfe14fe1c224d46a3e4135b48ffde6...7d157b61e198e3baca816129d8d406b300436e2f
> >
> > === Review kit
> >
> > The minimum set of steps needed to review the uploaded distribution
> > files in the Subversion repository can be summarized as follows:
> >
> >     # Check out the distribution
> >     svn co https://dist.apache.org/repos/... && cd $_
> >
> >     # Verify checksums
> >     shasum --check *.sha512
> >
> >     # Verify signatures
> >     wget -O - https://downloads.apache.org/logging/KEYS | gpg --import
> >     for sigFile in *.asc; do gpg --verify $sigFile; done
> >
> >     # Verify reproduciblity
> >     umask 0022
> >     unzip *-src.zip -d src
> >     cd src
> >     export NEXUS_REPO=https://repository.apache.org/content/...
> >     sh mvnw -Prelease verify artifact:compare
> -Dreference.repo=$NEXUS_REPO
> >     # If preferred, augment `mvnw` with `-DskipTests` to speed things up
> >
> > === Release notes
> >
> > This release delivers the first version of Log4j Docgen (Documentation
> > Generator).
> > It is a set of tools to auto-generate the Log4j plugin documentation (to
> be
> > integrated into the website) and the Log4j configuration XSD file (for
> > assisting the configuration of the Log4j runtime, i.e., `log4j2.xml`)
> from
> > the Log4j source code. See the project website for details.
> >
> > ==== Added
> >
> > * Add the `log4j-docgen` et al. containing a universal XML model to
> > document Log4j plugins
> >
> > ==== Changed
> >
> > * Move Log4j Changelog XML namespace and schema location to `
> > https://logging.apache.org/xml/ns` <https://logging.apache.org/xml/ns> <
> https://logging.apache.org/xml/ns>
> > and `
> > https://logging.apache.org/xml/ns/log4j-changelog-0.xsd`
> <https://logging.apache.org/xml/ns/log4j-changelog-0.xsd>
> > <https://logging.apache.org/xml/ns/log4j-changelog-0.xsd>, respectively
> >
> > ==== Removed
> >
> > * Remove `author` from Log4j Changelog. It was yet another bit to
> maintain
> > and created role-related (who did what) problems. Many modern software
> > projects use a VCS (e.g., Git) and support services (e.g., GitHub) which
> > make it trivial to trace back the origin of a change using commit and
> issue
> > IDs.
> >
> > ==== Updated
> >
> > * Update `org.apache.logging:logging-parent` to version `10.6.0`
> > * Update `jakarta.inject:jakarta.inject-api` to version `2.0.1` (#94)
> > * Update `org.apache.logging.log4j:log4j-core` to version `2.23.1` (#108)
> > * Update `org.apache.logging.log4j:log4j-plugins` to version
> `3.0.0-beta2`
> > (#107)
> > * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to
> > version `3.11.0` (#98)
> > * Update `org.assertj:assertj-core` to version `3.25.3` (#104)
> > * Update `org.codehaus.modello:modello-maven-plugin` to version `2.3.0`
> > (#105)
> > * Update `org.junit:junit-bom` to version `5.10.2` (#103)
> >
>

Reply via email to