Skip to content

Latest commit

 

History

History
89 lines (71 loc) · 4.36 KB

RELEASING.adoc

File metadata and controls

89 lines (71 loc) · 4.36 KB
Raw

Release instructions

Warning

In the code examples below, assuming the version to be released is 7.8.0.

Stage the release artifacts

  1. Checkout the release branch: git checkout -B release/7.8.0 origin/master

  2. Perform and commit following changes:

    1. Set the revision property to 7.8.0 in pom.xml

    2. Update the version and date in CHANGELOG.adoc

  3. Make sure that ./mvnw clean verify succeeds – if not, commit necessary fixes

  4. Push the release/7.8.0 branch

  5. Make sure the associated GitHub Actions workflow succeeds:

    1. Signed artifacts are uploaded to the Staging Repositories in repository.apache.org

    2. Signed sources are uploaded as GitHub Actions workflow artifacts

    If not, commit necessary fixes, push, and repeat.

  6. Close the repository in repository.apache.org

  7. Commit the signed sources (e.g., apache-log4j-tools-7.8.0-src.zip and apache-log4j-tools-7.8.0-src.zip.asc) to dist.apache.org/repos/dist/dev/logging/log4j Subversion repository

Vote the release

Collect release votes via email to [email protected] using the following template

The Apache Log4j Tools 7.8.0 release is now available for voting.

This release contains minor enhancements and bug fixes.

Source repository: https://github.com/apache/logging-log4j-tools
Branch: release/7.8.0
Commit: e82a44142280d013bd76ea18951fde00dcee192b
CI run: https://github.com/apache/logging-log4j-tools/actions/runs/3882476949
Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
Nexus repository: https://repository.apache.org/content/repositories/orgapachelogging-1096
Signing key: https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0&fingerprint=on&op=index

Please download, test, and cast your votes on the Log4j developers list.

[ ] +1, release the artifacts
[ ] -1, don't release, because...

The vote will remain open for 24 hours (or more if required). 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.
Warning

Make sure your email is sent in plain text, that is, no HTML! If you are using GMail, simply enable the "Plain text mode" while composing your message.

Publish the release

  1. Release the repository in repository.apache.org

  2. In dist.apache.org/repos/dist Subversion repository,

    1. move the signed sources from dev/logging/log4j directory to release/logging/log4j-tools/7.8.0

    2. delete files from an earlier release

    3. commit changes

  3. Report the release at reporter.apache.org

  4. Merge release/7.8.0 changes to master

  5. Set the revision property to the next development version (e.g., 7.9.0-SNAPSHOT) in pom.xml

  6. Update CHANGELOG.adoc accordingly

  7. Push the master branch

  8. Delete the release/7.8.0 branch

  9. Once the artifacts are visible in central.sonatype.dev, create a new release in GitHub

    1. Use the v7.8.0 tag created by the GitHub Actions workflow

    2. Copy necessary changes from CHANGELOG.adoc (formatting needs to be converted to Markdown!)