googleapis · Feb 21, 2018 · Feb 21, 2018 · Feb 21, 2018 · Feb 21, 2018 · Feb 21, 2018
diff --git a/README.md b/README.md
@@ -52,22 +52,24 @@ The easy way to get started is to add the umbrella package which pulls in all of
 dependencies. Note that even though the version of the umbrella package is Alpha, the individual clients are
 at different support levels (Alpha, Beta, and GA).
 
+[//]: # ({x-version-update-start:google-cloud:released})
 If you are using Maven, add this to your pom.xml file
 ```xml
 <dependency>
   <groupId>com.google.cloud</groupId>
   <artifactId>google-cloud</artifactId>
-  <version>0.35.0-alpha</version>
+  <version>0.36.0-alpha</version>
 </dependency>
 ```
 If you are using Gradle, add this to your dependencies
 ```Groovy
-compile 'com.google.cloud:google-cloud:0.33.0-alpha'
+compile 'com.google.cloud:google-cloud:0.36.0-alpha'
 ```
 If you are using SBT, add this to your dependencies
 ```Scala
-libraryDependencies += "com.google.cloud" % "google-cloud" % "0.33.0-alpha"
+libraryDependencies += "com.google.cloud" % "google-cloud" % "0.36.0-alpha"
 ```
+[//]: # ({x-version-update-end})
 
 It also works just as well to declare a dependency only on the specific clients that you need. See the README of
 each client for instructions.
@@ -275,19 +277,21 @@ Version Management
 
 The easiest way to solve version conflicts is to use google-cloud's BOM. In Maven, add the following to your POM:
 
+[//]: # ({x-version-update-start:google-cloud-bom:released})
 ```xml
   <dependencyManagement>
     <dependencies>
       <dependency>
         <groupId>com.google.cloud</groupId>
         <artifactId>google-cloud-bom</artifactId>
-        <version>0.35.0-alpha</version>
+        <version>0.36.0-alpha</version>
         <type>pom</type>
         <scope>import</scope>
       </dependency>
     </dependencies>
   </dependencyManagement>
 ```
+[//]: # ({x-version-update-end})
 
 This BOM is only available starting at version 0.32.0-alpha. If you are having problems with prior versions of
 google-cloud, use the following table as a reference to make sure that your versions are compatible. Definitions:

diff --git a/RELEASING.md b/RELEASING.md
@@ -78,41 +78,42 @@ To push a release version
 
 3. Verify that all unit and integration tests for the last commit have passed.
 
-4. Run `utilities/update_versions.sh` from the repository's base directory.
-This script takes optional arguments denoting the new versions for each qualifier (alpha, beta and/or GA). By default, if the current version is X.Y.Z-SNAPSHOT, the script will update the version in all the pom.xml and other relevant files to X.Y.Z. Please refer to the documentation in `utilities/update_versions.sh` for more details. Commit this version locally:
+4. Run `python utilities/bump_versions.py next_release minor` from the repository's base directory. (If there are only bug fixes and no additions to the surface, use `patch` instead of `minor`.) Alternatively, update the versions in `versions.txt` to the correct versions for the next release.
+
+5. Run `python utilities/replace_versions.py` from the repository's base directory. This updates the versions in all `pom.xml` and `README.md` files in preparation for a release. Commit these files locally:
 
   ```
   git add .
   git commit -m "Release [VERSION HERE]"
   ```
 
-1. Make sure you are using Maven version 3.3 or higher to support the Nexus plugin required to stage a release.
+6. Make sure you are using Maven version 3.3 or higher to support the Nexus plugin required to stage a release.
 
-1. To ensure a clean build, remove *all* Maven targets (including subdirectories not handled by `mvn clean`) by running `rm -rf target */target`.
+7. To ensure a clean build, remove *all* Maven targets (including subdirectories not handled by `mvn clean`) by running `rm -rf target */target`.
 
-5. Run `utilities/stage_release.sh`.
+8. Run `utilities/stage_release.sh`.
 This script builds and stages the release artifact on the Maven Central Repository, updates the README.md files with the release version + commits them locally, and finally generates a new site version for the gh-pages branch under a temporary directory named `tmp_gh-pages`. If you haven't run the release process before, it's worth verifying everything; check the staged release on the Sonatype website, and verify that the local commits have the right version updates.
 
 If you experience failures, you may need to:
 - repeat the clean step above
 - remove the temporary directory created to store docs by running `rm -rf tmp_gh-pages`
 - remove staged repositories from Sonatype (to prevent them from being released in subsequent steps): if a staged repository appears [here](https://oss.sonatype.org/#nexus-search;quick~com.google.cloud), remove it by running `mvn nexus-staging:drop`.
 
-6. Run `utilities/finalize_release.sh`.
+9. Run `utilities/finalize_release.sh`.
 This script will release the staged artifact on the Maven Central Repository and push the README.md and gh-pages updates to github.
 
-7. Publish a release on Github manually.
+10. Publish a release on Github manually.
 Go to the [releases page](https://github.com/GoogleCloudPlatform/google-cloud-java/releases) and open the appropriate release draft. Make sure the "Tag Version" is `vX.Y.Z` and the "Release Title" is `X.Y.Z`, where `X.Y.Z` is the release version as listed in the `pom.xml` files. 
 
   Add the commits since the last release into the release draft. Try to group them into sections with related changes. Anything that is a breaking change needs to be marked with `*breaking change*`. Such changes are only allowed for alpha/beta modules and `@BetaApi` features.
 
   Ensure that the format is consistent with previous releases (for an example, see the [0.1.0 release](https://github.com/GoogleCloudPlatform/google-cloud-java/releases/tag/v0.1.0)).  After adding any missing updates and reformatting as necessary, publish the draft.
 
-1. Create a new draft for the next release. Note any commits not included in the release that have been submitted before the release commit, to ensure they are documented in the next release.
+11. Create a new draft for the next release. Note any commits not included in the release that have been submitted before the release commit, to ensure they are documented in the next release.
 
-8. Run `utilities/update_versions.sh` again (to include "-SNAPSHOT" in the project version). Please refer to documentation in `utilities/update_versions.sh` for more details. 
+12. Run `python utilities/bump_versions next_snapshot patch` to include "-SNAPSHOT" in the current project version (Alternatively, update the versions in `versions.txt` to the correct versions for the next release.). Then, run `python utilities/replace_versions.py` to update the `pom.xml` files. (If you see updates in `README.md` files at this step, you probably did something wrong.)
 
-9. Create and merge in another PR to reflect the updated project version.  For an example of what this PR should look like, see [#227](https://github.com/GoogleCloudPlatform/google-cloud-java/pull/227).
+13. Create and merge in another PR to reflect the updated project version.  For an example of what this PR should look like, see [#227](https://github.com/GoogleCloudPlatform/google-cloud-java/pull/227).
 
 Improvements
 ============

diff --git a/google-cloud-bigquery/README.md b/google-cloud-bigquery/README.md
@@ -17,22 +17,24 @@ Java idiomatic client for [Google Cloud BigQuery][cloud-bigquery].
 
 Quickstart
 ----------
+[//]: # ({x-version-update-start:google-cloud-bigquery:released})
 If you are using Maven, add this to your pom.xml file
 ```xml
 <dependency>
   <groupId>com.google.cloud</groupId>
   <artifactId>google-cloud-bigquery</artifactId>
-  <version>0.35.0-beta</version>
+  <version>0.36.0-beta</version>
 </dependency>
 ```
 If you are using Gradle, add this to your dependencies
 ```Groovy
-compile 'com.google.cloud:google-cloud-bigquery:0.35.0-beta'
+compile 'com.google.cloud:google-cloud-bigquery:0.36.0-beta'
 ```
 If you are using SBT, add this to your dependencies
 ```Scala
-libraryDependencies += "com.google.cloud" % "google-cloud-bigquery" % "0.35.0-beta"
+libraryDependencies += "com.google.cloud" % "google-cloud-bigquery" % "0.36.0-beta"
 ```
+[//]: # ({x-version-update-end})
 
 Example Application
 -------------------

diff --git a/google-cloud-bigquery/pom.xml b/google-cloud-bigquery/pom.xml
@@ -2,7 +2,7 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <artifactId>google-cloud-bigquery</artifactId>
-  <version>0.35.0-beta</version>
+  <version>0.36.0-beta</version><!-- {x-version-update:google-cloud-bigquery:current} -->
   <packaging>jar</packaging>
   <name>Google Cloud BigQuery</name>
   <url>https://github.com/GoogleCloudPlatform/google-cloud-java/tree/master/google-cloud-bigquery</url>
@@ -12,7 +12,7 @@
   <parent>
     <groupId>com.google.cloud</groupId>
     <artifactId>google-cloud-pom</artifactId>
-    <version>0.35.0-alpha</version>
+    <version>0.36.0-alpha</version><!-- {x-version-update:google-cloud-pom:current} -->
   </parent>
   <properties>
     <site.installationModule>google-cloud-bigquery</site.installationModule>

diff --git a/google-cloud-bigquerydatatransfer/README.md b/google-cloud-bigquerydatatransfer/README.md
@@ -19,22 +19,24 @@ Transfer][cloud-bigquerydatatransfer].
 Quickstart
 ----------
 
+[//]: # ({x-version-update-start:google-cloud-bigquerydatatransfer:released})
 Add this to your pom.xml file
 ```xml
 <dependency>
   <groupId>com.google.cloud</groupId>
   <artifactId>google-cloud-bigquerydatatransfer</artifactId>
-  <version>0.35.0-beta</version>
+  <version>0.36.0-beta</version>
 </dependency>
 ```
 If you are using Gradle, add this to your dependencies
 ```Groovy
-compile 'com.google.cloud:google-cloud-bigquerydatatransfer:0.35.0-beta'
+compile 'com.google.cloud:google-cloud-bigquerydatatransfer:0.36.0-beta'
 ```
 If you are using SBT, add this to your dependencies
 ```Scala
-libraryDependencies += "com.google.cloud" % "google-cloud-bigquerydatatransfer" % "0.35.0-beta"
+libraryDependencies += "com.google.cloud" % "google-cloud-bigquerydatatransfer" % "0.36.0-beta"
 ```
+[//]: # ({x-version-update-end})
 
 Authentication
 --------------

diff --git a/google-cloud-bigquerydatatransfer/pom.xml b/google-cloud-bigquerydatatransfer/pom.xml
@@ -2,7 +2,7 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <artifactId>google-cloud-bigquerydatatransfer</artifactId>
-  <version>0.35.0-beta</version>
+  <version>0.36.0-beta</version><!-- {x-version-update:google-cloud-bigquerydatatransfer:current} -->
   <packaging>jar</packaging>
   <name>Google Cloud Bigquery Data Transfer</name>
   <url>https://github.com/GoogleCloudPlatform/google-cloud-java/tree/master/google-cloud-bigquerydatatransfer</url>
@@ -12,7 +12,7 @@
   <parent>
     <groupId>com.google.cloud</groupId>
     <artifactId>google-cloud-pom</artifactId>
-    <version>0.35.0-alpha</version>
+    <version>0.36.0-alpha</version><!-- {x-version-update:google-cloud-pom:current} -->
   </parent>
   <properties>
     <site.installationModule>google-cloud-bigquerydatatransfer</site.installationModule>