Minor updates to release docs

Use 'gerrit-review' instead of 'google' as the sample
git remote.  Add links to the index at the bottom.
Add tag example for subprojects.  Adjusted cmd line
examples to be more consistent.

Change-Id: I510481da127ef8eb885a5b30313b07fb7dbe3cba
This commit is contained in:
Martin Fick
2012-06-23 11:35:39 -06:00
parent 95ff3f00d8
commit ec31ff40e9
2 changed files with 23 additions and 9 deletions

View File

@@ -60,15 +60,15 @@ with this snapshot
* Deploy the snapshot: * Deploy the snapshot:
---- ====
mvn deploy mvn deploy
---- ====
Making a Gerrit Subproject Release Making a Gerrit Subproject Release
---------------------------------- ----------------------------------
* First deploy (and test) the latest snapshot for this subprojects * First deploy (and test) the latest snapshot for the subproject
* Update the top level pom.xml in the subproject to reflect the new project * Update the top level pom.xml in the subproject to reflect the new project
version (the exact value of the tag you will create below) version (the exact value of the tag you will create below)
@@ -77,8 +77,18 @@ version (the exact value of the tag you will create below)
* Tag the version you just pushed (and push the tag) * Tag the version you just pushed (and push the tag)
====
git tag -a -m "prolog-cafe 1.3" v1.3
git push gerrit-review refs/tags/v1.3:refs/tags/v1.3
====
* Deploy the new release: * Deploy the new release:
---- ====
mvn deploy mvn deploy
---- ====
GERRIT
------
Part of link:index.html[Gerrit Code Review]

View File

@@ -130,8 +130,8 @@ Tag
* Push the New Tag * Push the New Tag
==== ====
git push google refs/tags/v2.5-rc0:refs/tags/v2.5-rc0 git push gerrit-review refs/tags/v2.5-rc0:refs/tags/v2.5-rc0
git push google refs/tags/v2.5:refs/tags/v2.5 git push gerrit-review refs/tags/v2.5:refs/tags/v2.5
==== ====
@@ -192,8 +192,7 @@ because Status=Submitted is considered a closed issue.
Mailing List Mailing List
~~~~~~~~~~~~ ~~~~~~~~~~~~
* Send an email to the mailing list to announce the release * Send an email to the mailing list to announce the release, consider including some or all of the following in the email:
* Consider including some or all of the following in the email:
** A link to the release and the release notes (if a final release) ** A link to the release and the release notes (if a final release)
** A link to the docs ** A link to the docs
** Describe the type of release (stable, bug fix, RC) ** Describe the type of release (stable, bug fix, RC)
@@ -237,3 +236,8 @@ ensure that none of the fixes ever get lost.
git branch -f stable origin/stable git branch -f stable origin/stable
git merge stable git merge stable
==== ====
GERRIT
------
Part of link:index.html[Gerrit Code Review]