Skip to content

[WIP] NG Release Process

Peter Kirschner edited this page May 13, 2026 · 1 revision

Next Generation Release Process

Starting point is the development on the master branch

Phase 1: build RC1

Release process is started by pushing a tag rel_{rel_ver} e.g. rel_7.3.1 This triggers release workflow in build system and therefor the release.sh script

  1. new branch for the release is created, with the name rel_{rel_ver} e.g. rel_7.3.1
  2. change versions from {prev_ver}-SNAPSHOT to {prev_ver}-RC1
  3. in file cnf/build.bnd and gradle.properties, gradle-plugins/gradle.properties
    update the property bnd_version: to bnd_version: {rel_ver}-RC1
  4. in file maven-plugins/bnd-plugin-parent/pom.xml update the tag <revision>{prev_ver}-SNAPSHOT</revision> to <revision>{rel_ver}-RC1</revision>
  5. verify build and deployments in 1. JFrog https://bndtools.jfrog.io/artifactory/libs-release/ 2. Sonatype deployments - verify the deployment ids
  6. When successful update via curl REST API the update-rc - https://bndtools.jfrog.io/ui/admin/repositories/virtual/update-rc/edit
  7. announce the release {rel_ver}-RC1

Phase 2: verify RC - and update if required

  1. checkout the branch rel_ver
  2. cherry-pick bugfix commits from branch master
  3. push new tag {rel_ver}-RCn
  4. in file cnf/build.bnd and gradle.properties, gradle-plugins/gradle.properties
    update the property bnd_version: to bnd_version: {rel_ver}-RCn
  5. in file maven-plugins/bnd-plugin-parent/pom.xml update the tag <revision>{prev_ver}.*</revision> to <revision>{rel_ver}-RCn</revision>
  6. verify build and deployments in 1. JFrog https://bndtools.jfrog.io/artifactory/libs-release/ 2. Sonatype deployments - verify the deployment ids
  7. When successful update via curl REST API the update-rc - https://bndtools.jfrog.io/ui/admin/repositories/virtual/update-rc/edit
  8. announce the release {rel_ver}-RCn

Phase 3: build GA

to be continued

Clone this wiki locally