dev-release: Point to Gerrit docs for info
The Gerrit artifact deployment doc has info on PGP key and Google Cloud
Storage setup that is necessary for making a Gitiles release. Provider a
pointer so that someone making a Gitiles release can find it.
Also, clarify that the git tag should be PGP signed.
diff --git a/Documentation/developer-guide.md b/Documentation/developer-guide.md
index 398a2e7..1716e80 100644
@@ -115,7 +115,10 @@
Gitiles artifacts are published to the [gerrit-maven
bucket](http://gerrit-maven.storage.googleapis.com/). To release a new version,
-you must have write access to this bucket.
+you must have write access to this bucket. See
+for PGP key setup and Google Cloud Storage access setup.
First, increment `GITILES_VERSION` in `version.bzl`. Technically, Gitiles uses
@@ -129,7 +132,8 @@
-Tag the release with an annotated tag matching the version number.
+Tag the release with a signed, annotated tag matching the version number, for
Once released, Maven projects can consume the new version as long as they point
at the proper repository URL. Similarly, Bazel projects using the `maven_jar`