This repository has been archived by the owner on May 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 385
Release Process
Aaron Schlesinger edited this page May 9, 2017
·
33 revisions
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.
- Ensure that all PRs in the milestone are merged, or move them out to the next appropriate open milestone
- Ensure that all issues in the milestone are closed. Any open issues not automatically closed by PRs in the milestone should be manually closed with an explanatory comment
- Close the milestone that will be released
-
Create a new GitHub release, using
v$MILESTONE
as the tag name (for example, if the milestone is0.0.1
, the tag name should bev0.0.1
) - Travis will automatically build and push Docker images to our quay.io repository with the newly released Git tag
- After all images are in Quay, submit a single pull request to do all of the following:
- Updates all documentation (i.e. the walkthrough) to reference the newly tagged images
- Submit a pull reuqest to update the charts/catalog and charts/ups-broker
values.yaml
files to reference the new image tags