Adapt Release Docs
* Remove section about subprojects as they are released independently
* Lowercase the usage of 'rc' as branches and artifacts are all lower case as well
Change-Id: Id1552ab33c9a5af8e16ecfec5578e50cd3c742ed
diff --git a/Documentation/dev-release.txt b/Documentation/dev-release.txt
index 2a857b2..5e07fc7 100644
--- a/Documentation/dev-release.txt
+++ b/Documentation/dev-release.txt
@@ -16,8 +16,8 @@
== Gerrit Release Type
Here are some guidelines on release approaches depending on the
-type of release you want to make (`stable-fix`, `stable`, `RC0`,
-`RC1`...).
+type of release you want to make (`stable-fix`, `stable`, `rc0`,
+`rc1`...).
[[stable]]
=== Stable
@@ -27,19 +27,19 @@
* Propose the release with any plans/objectives to the mailing list
-* Create a Gerrit `RC0`
+* Create a Gerrit `rc0`
-* If needed create a Gerrit `RC1`
+* If needed create a Gerrit `rc1`
[NOTE]
You may let in a few features to this release
-* If needed create a Gerrit `RC2`
+* If needed create a Gerrit `rc2`
[NOTE]
There should be no new features in this release, only bug fixes
-* Finally create the `stable` release (no `RC`)
+* Finally create the `stable` release (no `rc`)
=== Stable-Fix
@@ -75,7 +75,6 @@
To create a Gerrit release the following steps have to be done:
-. link:#subproject[Release Subprojects]
. link:#build-gerrit[Build the Gerrit Release]
. link:#publish-gerrit[Publish the Gerrit Release]
.. link:#publish-to-maven-central[Publish the Gerrit artifacts to Maven Central]
@@ -90,34 +89,10 @@
. link:#merge-stable[Merge `stable` into `master`]
-[[subproject]]
-=== Release Subprojects
-
-The subprojects to be released are:
-
-* `gwtjsonrpc`
-* `gwtorm`
-* `prolog-cafe`
-
-For each subproject do:
-
-* Check the dependency to the Subproject in the Gerrit parent `pom.xml`:
-+
-If a `SNAPSHOT` version of the subproject is referenced the subproject
-needs to be released so that Gerrit can reference a released version of
-the subproject.
-
-* link:dev-release-subproject.html#make-snapshot[Make a snapshot and test it]
-* link:dev-release-subproject.html#prepare-release[Prepare the Release]
-* link:dev-release-subproject.html#publish-release[Publish the Release]
-
-* Update the `artifact`, `sha1`, and `src_sha1` values in the `maven_jar`
-for the Subproject in `WORKSPACE` to the released version.
-
[[update-versions]]
=== Update Versions and Create Release Tag
-Before doing the release build, the `GERRIT_VERSION` in the `VERSION`
+Before doing the release build, the `GERRIT_VERSION` in the `version.bzl`
file must be updated, e.g. change it from `2.5-SNAPSHOT` to `2.5`.
In addition the version must be updated in a number of pom.xml files.
@@ -383,7 +358,7 @@
Use the `version` tool to set the version in the `version.bzl` file:
----
- ./tools/version.py 2.11-SNAPSHOT
+ ./tools/version.py 2.6-SNAPSHOT
----
Verify that the changes made by the tool are sane, then commit them, push
