Skip to content

Add verification step to release instructions #269

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

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

ppkarwasz
Copy link
Contributor

Although it might be obvious that Release Managers should abide to the same rules as the other voters, this should be stated explicitly. This PR:

  • Explicitly asks Release Managers to perform a verification step, before sending the release vote.
  • Adds per-project CI workflows that need to run on the generated artifacts. For Log4j there is an integration-test.yaml in samples that verifies the compatibility of the release with JLink, GraalVM and Android.

Although it might be obvious that Release Managers should abide to the same rules as the other voters, this should be stated explicitly.
This PR:

- Explicitly asks Release Managers to perform a verification step, **before** sending the release vote.
- Adds per-project CI workflows that need to run on the generated artifacts. For Log4j there is an `integration-test.yaml` in samples that verifies the compatibility of the release with JLink, GraalVM and Android.
@ppkarwasz ppkarwasz merged commit 9c8e174 into main Oct 16, 2024
@ppkarwasz ppkarwasz deleted the doc/release-verification branch October 16, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants