Skip to content

Latest commit

 

History

History
42 lines (35 loc) · 1.62 KB

RELEASE.md

File metadata and controls

42 lines (35 loc) · 1.62 KB
Raw

Release process

The release process described below uses the 'current' branch. For patch releases see the Patch releases section below

On the 11th of the month

  1. Create release-X.Y.Z branch from current
  2. Wait for the build on the release-X.Y.Z branch to complete
  3. If the build was not successful
    1. Checkout the release-X.Y.Z branch
    2. Apply whatever fixes are needed
    3. Commit and push them to release-X.Y.Z branch
    4. Redo steps #2 and #3
  4. On the current branch update the POMs to point to the next SNAPSHOT version

On the 13th of the month

  1. Trigger release using release-X.Y.Z as branch to release from
  2. If release build fails
    1. Remove the vX.Y.Z tag
    2. Checkout the release-X.Y.Z branch
    3. Apply whatever fixes are needed
    4. Commit and push them to release-X.Y.Z
    5. Retrigger the release
  3. Trigger release docs workflow
  4. Create release notes
  5. Set correct tag for release notes
  6. Make sure “Create a discussion for this release” is checked
  7. Make sure Category is set to General
  8. Publish release notes
  9. Wait for release bits to show up on Maven Central
  10. On the piranha_cloud Twitter announce that Piranha X.Y.Z has been released and make sure to thank our contributors.
  11. Apply fixes from release-X.Y.Z branch to the current branch with a corresponding issue (if any).
  12. Delete the release-X.Y.Z branch
  13. Close the milestone on GitHub

Patch releases

If you are creating a patch release against a branch please follow all the steps above and replace current with the branch you are patching against where appropriate (without waiting a day in between).