Update usage of the 'version' tool in the release documentation
The documentation was referring to 'version.sh' but the file is actually called 'version.py'. Also fix a couple of minor grammar and formatting issues. Change-Id: Ib3a6fbab8a87be42adf9975310a1597fa22f65ea
This commit is contained in:
@@ -122,18 +122,19 @@ for the Subproject in `/lib/BUCK` to the released version.
|
||||
[[update-versions]]
|
||||
=== Update Versions and Create Release Tag
|
||||
|
||||
Before doing the release build the `GERRIT_VERSION` in the `VERSION`
|
||||
file must be updated, e.g. change if from `2.5-SNAPSHOT` to `2.5`.
|
||||
Before doing the release build, the `GERRIT_VERSION` in the `VERSION`
|
||||
file must be updated, e.g. change it from `2.5-SNAPSHOT` to `2.5`.
|
||||
|
||||
In addition the version must be updated in a number of pom.xml files.
|
||||
To do this run the `./tools/version.sh` script and provide the new
|
||||
|
||||
To do this run the `./tools/version.py` script and provide the new
|
||||
version as parameter, e.g.:
|
||||
|
||||
----
|
||||
./tools/version.sh 2.5
|
||||
./tools/version.py 2.5
|
||||
----
|
||||
|
||||
Commit the changes and create the release tag on the new commit:
|
||||
Commit the change and create the release tag on the new commit:
|
||||
|
||||
----
|
||||
git tag -a v2.5
|
||||
|
||||
Reference in New Issue
Block a user