dev-release: fix order of artifact deployment
The artifacts should be built and deployed to Maven Central first,
and then the same WAR file should be deployed to the Google Storage.
If it's the other way round, we end up with a different WAR file on
each place.
Change-Id: Ie60035bced2772c0a39ed9c3f2a92eb4163ff5b2
diff --git a/Documentation/dev-release.txt b/Documentation/dev-release.txt
index 1b3e98f..6abfb9e 100644
--- a/Documentation/dev-release.txt
+++ b/Documentation/dev-release.txt
@@ -84,8 +84,8 @@
. link:#subproject[Release Subprojects]
. link:#build-gerrit[Build the Gerrit Release]
. link:#publish-gerrit[Publish the Gerrit Release]
-.. link:#extension-and-plugin-api[Publish the Extension and Plugin API Jars]
-.. link:#publish-gerrit-war[Publish the Gerrit WAR (with Core Plugins)]
+.. link:#publish-to-maven-central[Publish the Gerrit artifacts to Maven Central]
+.. link:#publish-to-google-storage[Publish the Gerrit WAR to Google Storage]
.. link:#push-stable[Push the Stable Branch]
.. link:#push-tag[Push the Release Tag]
.. link:#upload-documentation[Upload the Documentation]
@@ -168,15 +168,6 @@
[[publish-gerrit]]
=== Publish the Gerrit Release
-[[publish-gerrit-war]]
-==== Publish the Gerrit WAR (with Core Plugins)
-
-* Upload the WAR to the Google Cloud Storage
-
-** go to https://console.developers.google.com/project/164060093628/storage/gerrit-releases/
-** make sure you are signed in with your Gmail account
-** manually upload the Gerrit WAR file by using the `Upload` button
-
[[publish-to-maven-central]]
==== Publish the Gerrit artifacts to Maven Central
@@ -306,6 +297,13 @@
** Select `com.google.gerrit` as `Project`.
+[[publish-to-google-storage]]
+==== Publish the Gerrit WAR to the Google Cloud Storage
+
+* go to https://console.developers.google.com/project/164060093628/storage/gerrit-releases/
+* make sure you are signed in with your Gmail account
+* manually upload the Gerrit WAR file by using the `Upload` button
+
[[push-stable]]
==== Push the Stable Branch
