diff options
Diffstat (limited to 'Documentation/dev-release.txt')
| -rw-r--r-- | Documentation/dev-release.txt | 21 |
1 files changed, 15 insertions, 6 deletions
diff --git a/Documentation/dev-release.txt b/Documentation/dev-release.txt index 2f6a7d6939..039d545d24 100644 --- a/Documentation/dev-release.txt +++ b/Documentation/dev-release.txt @@ -89,14 +89,22 @@ To create a Gerrit release the following steps have to be done: . link:#merge-stable[Merge `stable` into `master`] -[[update-version]] -=== Update Version and Create Release Tag +[[update-versions]] +=== Update Versions and Create Release Tag Before doing the release build, the `GERRIT_VERSION` in the `version.bzl` file must be updated, e.g. change it from `2.5-SNAPSHOT` to `2.5`. -Commit the change in `version.bzl` and create a signed release tag on the -new commit: +In addition the version must be updated in a number of pom.xml files. + +To do this run the `./tools/version.py` script and provide the new +version as parameter, e.g.: + +---- + ./tools/version.py 2.5 +---- + +Commit the changes and create a signed release tag on the new commit: ---- git tag -s -m "v2.5" v2.5 @@ -139,8 +147,9 @@ Verify the versions: link:dev-release-deploy-config.html#deploy-configuration-setting-maven-central[ configuration] for deploying to Maven Central -* Make sure that the version is updated in the `version.bzl` file as described -in the link:#update-version[Update Version and Create Release Tag] section. +* Make sure that the version is updated in the `version.bzl` file and in +the `pom.xml` files as described in the link:#update-versions[Update +Versions and Create Release Tag] section. * Push the WAR to Maven Central: + |