release-v2.1.0

[mattysweeps]

Release Process

Before continuing

• [x] make lint build test bosh-release tile runs successfully
• [x] The system should build and all tests pass with the Concourse pipeline.
• [x] Open a ticket with the name release-vX.Y.Z and copy the contents of this file into its description.
• [x] Create a new pre-release branch in the GitHub repository labeled release-vX.Y.Z.

Update the project in the branch

• [x] Update the CHANGELOG.md to match the new version.
• [x] Ensure tile.yml.erb is using the correct PCF version dependencies.
• [x] Commit the changes on the new branch.

Our repository

• [x] Draft a new release in GitHub with the tag vX.Y.Z-rc
• [x] Include the version's changelog entry in the description.
• [x] Upload the built tile and BOSH release to the pre-release.
• [x] Check the box labeled This is a pre-release.
• [x] Publish the pre-release.

Release on PivNet

• [x] Validate that the name in the generated tile's metadata.yml matches the slug on PivNet.
• [x] Ensure the release version is consistent on the tile and documentation.
• [x] Create a new release on PivNet as an Admin Only release.
• [x] Upload the tile and BOSH release that were staged to GitHub.
• [x] Check that the tile passes the tests in the build dashboard.

Upgrade the documentation

• [x] Submit a pull request to the documentation repository.
• [x] 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

• [x] Fill out the release form.
• [x] An ISV Program Manager will make the release available to "All Users" after review. Partner Admins can make the release available to "Admin Users".
• [x] Merge the release branch once done.
• [ ] Submit an issue to https://github.com/cf-platform-eng/gcp-pcf-quickstart to update the GCP PCF quickstart.

[evandbrown]

Thanks, @mattysweeps! A few things:

• [x] Is 2.3.0 the right version? The last release was 2.0.1.
• [x] Versions in metadata/stackdriver-nozzle.yml (inside the .pivotal file) currently have an -rc suffix. The -rc suffix should only be used in the description/tags on GitHub, and should be omitted from the tile itself.

[mattysweeps]

@evandbrown the -rc suffix should be removed in 2.3.0-rc2 https://github.com/cloudfoundry-community/stackdriver-tools/releases/tag/v2.3.0-rc2

Yes, 2.3.0 is the correct version. To my knowledge, no backwards incompatible tile configuration or behavior (except the removal of the duplication of the log message) has been added. And 2.3.0 is a close and convenient minor bump to use since it pairs itself with PCF 2.3 support.

The decision process and/or the ABI coverage we choose for tile versioning can be improved and better defined for later releases.

[evandbrown]

Cool! So did we use 2.1.0 and 2.2.0 in releases that didn't make it to Pivnet?

[mattysweeps]

No, I just think it should be 2.3.0

[evandbrown]

Since we're following semver shouldn't we bump minor and call this 2.1.0? I don't think we want to conflate the tile version with support for a particular version of PAS.

[mattysweeps]

@evandbrown I've changed the version to 2.1.0 per your request: https://github.com/cloudfoundry-community/stackdriver-tools/releases/tag/v2.1.0-rc

[evandbrown]

Result from Tile Dashboard: {"errors":["Product Stackdriver Nozzle depends on Small Footprint PAS (~\u003e 2.3.0). Please deploy it first or as a part of this selective deploy."]}

I'll crack the tile open and see if I can change that to get through CI.

[mattysweeps]

@evandbrown see https://github.com/cloudfoundry-community/stackdriver-tools/releases/tag/v2.1.0-rc2

[mattysweeps]

2.1.0 is released:

https://github.com/cloudfoundry-community/stackdriver-tools/releases/tag/v2.1.0 https://network.pivotal.io/products/gcp-stackdriver-nozzle/#/releases/282380