anchor.diff:  = Spring Cloud GCP release process
   
  -The actual release process is triggered by the release admin.
  +All scripts can be found in the `.kokoro` directory.
  +
  +
  +## Snapshots
  +
  +A commit to the `master` branch will automatically trigger the `prod:cloud-java-frameworks/spring-cloud-gcp/continuous` job that will publish snapshots to link:https://oss.sonatype.org/content/repositories/snapshots/com/google/cloud/spring-cloud-gcp/[Sonatype Snapshots repository].
  +
  +
  +## Releases
  +
   As opposed to the 1.x releases, the 2.0 release happens independent of the Spring Cloud release train.
   To simplify the process, perform this list of prerequisites before asking the release admin to run the release scripts.
   
   . Ensure that modules that shouldn't be released are not included in the `<modules>` block in the `release` profile of `pom.xml`.
  -For GA releases this should be configured under the `central` Maven profile.
  -+
  +
   [source,xml]
   ----
   <profile>
  
positive.code: </profile>
  ----
  
  . Ensure all Maven commands listed in `.kokoro/stage.sh` script can be executed successfully locally.
  You can add `-Dgpg.skip` in place of the actual GPG key locally.
  
  . Invoke the Kokoro `stage` job.
  Log in to OSS Sonatype and verify the contents of the staged package.
  
  . Invoke to the Kokoko `promote` job.
  
  . Make sure that the link:https://github.com/spring-io/start.spring.io/blob/master/start-site/src/main/resources/application.yml[Spring Boot Initializr] is updated to support the new version of Spring Cloud GCP.
  
  == Uploading Javadocs
  
  After releasing a new version of Spring Cloud GCP, you will need to upload the javadocs for the released version.
  By this point, we assume that a new release branch has been created for project (such as `2.0.x`, `2.1.x`, etc.).
  
  The latest version of the docs can be accessed at the `latest/` url:
  https://googleapis.dev/java/spring-cloud-gcp/latest/index.html
  
negative.code: +
  Example: If you published the javadocs for version `2.0.0-SNAPSHOT`, then the URL would be: https://googleapis.dev/java/spring-cloud-gcp/2.0.0-SNAPSHOT/index.html
  
  
  == Updating Spring Documentation
  . (TODO): Update GitHub Pages to publish the refdoc for the newly released version.
  
  . For GA releases, ask on the https://gitter.im/spring-cloud-gcp/Lobby[Spring Cloud GCP Gitter] for the Spring team to update the https://spring.io/projects/spring-cloud-gcp#learn[API Documentation link] to point to the newly published Ref doc and Javadocs.
  
  . Smoke test changes by running through a handful of our link:https://codelabs.developers.google.com/spring[Spring Cloud GCP codelabs] with the newly release version.
  Update the instructions as needed.
  