From cf2da292e9512948c768fa8d11b4d8ca5b7b368b Mon Sep 17 00:00:00 2001
From: Joseph Lewis III <jlewisiii@google.com>
Date: Wed, 19 Sep 2018 13:31:49 -0700
Subject: [PATCH] starting v4.0 release process

---
 CHANGELOG.md                               |  2 ++
 brokerapi/brokers/models/service_broker.go |  4 +--
 docs/releasing.md                          | 37 +++++++++++++++++++---
 3 files changed, 37 insertions(+), 6 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index b19db216d..01e7aae11 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unresolved]
 
+## [4.0.0] - 2018-10-01
+
 ### Added
 - New sub-command `plan-info` to dump plan information to the console.
 - New sub-command `client` to execute documentation examples and interact with the broker.
diff --git a/brokerapi/brokers/models/service_broker.go b/brokerapi/brokers/models/service_broker.go
index 455283e13..108c02dc1 100755
--- a/brokerapi/brokers/models/service_broker.go
+++ b/brokerapi/brokers/models/service_broker.go
@@ -50,10 +50,10 @@ type ServiceAccountManager interface {
 // This custom user agent string is added to provision calls so that Google can track the aggregated use of this tool
 // We can better advocate for devoting resources to supporting cloud foundry and this service broker if we can show
 // good usage statistics for it, so if you feel the need to fork this repo, please leave this string in place!
-var CustomUserAgent = "cf-gcp-service-broker-test 3.6.0"
+var CustomUserAgent = "cf-gcp-service-broker-test 4.0.0"
 
 func ProductionizeUserAgent() {
-	CustomUserAgent = "cf-gcp-service-broker 3.6.0"
+	CustomUserAgent = "cf-gcp-service-broker 4.0.0"
 }
 
 const CloudPlatformScope = "https://www.googleapis.com/auth/cloud-platform"
diff --git a/docs/releasing.md b/docs/releasing.md
index f3cc54ccd..fd1f5eb56 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -1,13 +1,42 @@
 # Release Process
 
-## Pre-Check
+## Before continuing
 
-- [ ] The system should build and all tests pass with the concourse pipeline.
+- [ ] The system should build and all tests pass with the Concourse pipeline.
+- [ ] Open a ticket with the name `release-vX.Y.Z` and copy the contents of this file into its description.
+- [ ] Create a new pre-release branch in the GitHub repository labeled `release-vX.Y.Z`.
 
-## Generating the OSDF file
+## Generate the OSDF file
 
 - [ ] Get a list of licenses using the [license_finder](https://github.com/pivotal-legacy/LicenseFinder) tool.
 - [ ] Fill in the [license template](https://docs.google.com/spreadsheets/d/1gqS1jwmpSIEdgTadQXhkbQqhm1hO3qOU1-AWwIYQqnw/edit#gid=0) with them.
 - [ ] Download it as a CSV.
 - [ ] Upload the CSV to the [OSDF Generator](http://osdf-generator.cfapps.io/static/index.html) and download the new OSDF file.
-- [ ] Create a new pre-release tag in the git repository.
+- [ ] Replace the current OSDF file in the root of the project with the OSDF for the release and commit the change.
+
+## Our repository
+
+- [ ] Draft a new release in GitHub with the tag `vX.Y.Z-rc`
+- [ ] Include the version's changelog entry in the description.
+- [ ] Upload the built tile and OSDF to the pre-release.
+- [ ] Check the box labeled **This is a pre-release**.
+- [ ] Publish the pre-release.
+
+## Release on PivNet
+
+- [ ] Validate that the name in the generated tile's `metadata.yml` matches the slug on PivNet.
+- [ ] Ensure the release version is consistent on the tile and documentation.
+- [ ] Create a [new release on PivNet](network.pivotal.io) as an Admin Only release.
+- [ ] Upload the tile and OSDF files that were staged to GitHub.
+- [ ] Check that the tile passes the tests in the [build dashboard](https://tile-dashboard.cfapps.io/tiles/gcp-service-broker).
+
+## Upgrade the documentation
+
+- [ ] Submit a pull request to the [documentation repository](https://github.com/pivotal-cf/docs-google/tree/master/docs-content).
+- [ ] Include the new release notes, changes, and the ERT/PAS and Ops Managers versions, as well as your Product Version and Release Date in the Product Snapshot on PivNet.
+
+## File for release
+
+- [ ] Fill out the [release form](https://docs.google.com/forms/d/e/1FAIpQLSctLGMU8iOuwq6NqDYI65aMhJ7widDQGo9SawDG0b8TFfq7Ag/viewform).
+- [ ] An ISV Program Manager will make the release available to "All Users" after review. Partner Admins can make the release available to "Admin Users".
+- [ ] Merge the release branch once done.