GoogleCloudPlatform/gcp-service-broker

release-v5.0.0

Closed this issue · 0 comments

josephlewis42 commented

Release Process

Before continuing

  • 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.

Update the project in the branch

  • Update version in utils/version.go.
  • Run go build.
  • Run ./gcp-service-broker generate tile > tile.yml.
  • Run ./gcp-service-broker generate manifest > manifest.yml.
  • Run ./gcp-service-broker generate use --destination-dir="docs/".
  • Run ./gcp-service-broker generate customization > docs/customization.md.
  • Update the CHANGELOG.md to match the new version.
  • Commit the changes on the new branch.

Generate the OSDF file

  • Get a list of licenses using the license_finder tool.
  • Fill in the license template with them.
  • Download it as a CSV.
  • Upload the CSV to the OSDF Generator and download the new OSDF file.
  • 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 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.

Upgrade the documentation

  • Submit a pull request to the documentation repository.
  • 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.
  • 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.
  • Make a release announcement in the gcp-service-broker Google Group like this one.
  • Submit an issue to https://github.com/cf-platform-eng/gcp-pcf-quickstart to update the GCP PCF quickstart.