Skip to content

Latest commit

 

History

History
27 lines (22 loc) · 1.42 KB

RELEASE.md

File metadata and controls

27 lines (22 loc) · 1.42 KB

Releasing the parent-oss project

WARN: Due to some internal tooling (releasability checks) semantic versioning is barely supported.

Therefore, a new release number has to be a new major.

Assume you want to release from version 70.0.0.x, the next version must be 71.0.0.x

  1. Prepare a new project release in Jira with as version 71.0 (no patch or build number)

  2. Leave the Jira version status as UNRELEASED

  3. Update pom.xml version of parent-oss project. (example PR)

  4. Check that releasability checks pass on Burgr

  5. Retrieve the last build number on Burgr (major.minor.patch.build-number)

  6. On GitHub create a new release and set this number retrieved from Burgr as tag and release version

  7. Publish the release

  8. Check that the GitHub release workflow run well

  9. Check it is gracefully deployed on Sonatype.

WARN: It can take up to 24h to have the release synchronized with Sonatype. Sometimes it is very fast sometimes not)