Mention the version.py tool in the release documentation
Change-Id: I7448d89a4239a1e584ce82c12f701f6ff83227e4
This commit is contained in:
parent
6928a0f1c5
commit
f7c9f2cc81
@ -405,11 +405,19 @@ including some or all of the following in the email:
|
||||
[[increase-version]]
|
||||
=== Increase Gerrit Version for Current Development
|
||||
|
||||
All new development that is done in the `master` branch will be
|
||||
included in the next Gerrit release. Update the Gerrit version in the
|
||||
`VERSION` file, and plugin archetypes' `pom.xml` files. Push the change
|
||||
for review and get it merged.
|
||||
All new development that is done in the `master` branch will be included in the
|
||||
next Gerrit release. The Gerrit version should be set to the snapshot version
|
||||
for the next release.
|
||||
|
||||
Use the `version` tool to set the version in the `VERSION` file and plugin
|
||||
archetypes' `pom.xml` files:
|
||||
|
||||
----
|
||||
./tools/version.py 2.11-SNAPSHOT
|
||||
----
|
||||
|
||||
Verify that the changes made by the tool are sane, then commit them, push
|
||||
the change for review on the master branch, and get it merged.
|
||||
|
||||
[[merge-stable]]
|
||||
=== Merge `stable` into `master`
|
||||
|
Loading…
Reference in New Issue
Block a user