---

ajkannan · ajkannan · commit 26d7cee34e7a · 2015-10-09T16:26:24.000-07:00
yaml --- r: 6263 b: refs/heads/tswast-patch-1 c: c1d1fb7 h: refs/heads/master i: 6261: 15a9183 6259: 15c6123 6255: 3d1444c
diff --git a/[refs] b/[refs]
@@ -57,5 +57,5 @@ refs/tags/v0.18.0: 9d193c4c4b9d1c6f21515dd8e50836b9194ec9bb
 refs/tags/v0.19.0: e67b56e4d8dad5f9a7b38c9b2107c23c828f2ed5
 refs/tags/v0.20.0: 839f7fb7156535146aa1cb2c5aadd8d375d854e8
 refs/tags/v0.20.1: 370471f437f1f4f68a11e068df5cd6bf39edb1fa
-refs/heads/tswast-patch-1: 2f0bf9ace6020d10b7c47cf4d3b8781c7c77fd70
+refs/heads/tswast-patch-1: c1d1fb72463009421db951e618b67dd1885c1053
 refs/heads/pubsub-streaming-pull: 19262b752ee874eb2ca3b950eb2aef44d5a5267b
diff --git a/branches/tswast-patch-1/RELEASING.md b/branches/tswast-patch-1/RELEASING.md
@@ -24,4 +24,4 @@ Pushing a snapshot is completely automated.  If "-SNAPSHOT" is included in the v
 
 ### Improvements
 
-Automatic tagging is not currently implemented, though it was discussed in #119.  If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases.  However, automatically creating useful annotations for this tag will be difficult.  Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.
+Automatic tagging is not currently implemented, though it was discussed in [#119](https://github.com/GoogleCloudPlatform/gcloud-java/pull/119).  If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases.  However, automatically creating useful annotations for this tag will be difficult.  Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.

Original file line number	Diff line number	Diff line change
`@@ -24,4 +24,4 @@ Pushing a snapshot is completely automated. If "-SNAPSHOT" is included in the v`
`24`	`24`
`25`	`25`	`### Improvements`
`26`	`26`
`27`		-Automatic tagging is not currently implemented, though it was discussed in #119. If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases. However, automatically creating useful annotations for this tag will be difficult. Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.
	`27`	+Automatic tagging is not currently implemented, though it was discussed in [#119](https://github.com/GoogleCloudPlatform/gcloud-java/pull/119). If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases. However, automatically creating useful annotations for this tag will be difficult. Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.