Release Process

This document is for core maintainers who will release a new version of the service catalog. Releases are listed on the milestones page.

The step-by-step instructions below should be followed to release a new version of service-catalog.

The Day Before the Release

1. Ensure that all PRs in the milestone are merged, or move them out to the next appropriate open milestone
2. Ensure that all issues in the milestone are closed or moved, as appropriate. Any open issues not automatically closed by PRs in the milestone should be manually closed with an explanatory comment

The Day of the Release

1. Close the milestone that will be released
2. Create a new GitHub release, using v$MILESTONE as the tag name (for example, if the milestone is 0.0.1, the tag name should be v0.0.1)
3. Travis will automatically build and push Docker images to our quay.io repository with the newly released Git tag
4. After all images are in Quay, submit a single pull request to do all of the following:
   1. Updates all documentation (i.e. the walkthrough) to reference the newly tagged images
   2. Submit a pull request to update the charts/catalog and charts/ups-broker values.yaml files to reference the new image tags
   3. After that PR passes CI, you can merge it w/o review
   4. Once the PR is merged, make sure to close the milestone