-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate release process #1027
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Milestone
Comments
minherz
added
type: process
A process-related concern. May include testing, release, or the like.
priority: p3
Desirable enhancement or fix. May not be included in next release.
labels
Apr 21, 2023
Commenting because this is "near out-of-SLO":
|
@minherz I just found your Google-internal doc called "Cloud Ops Sandbox Release Process". That's helpful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Description
Evaluate release-please bot vs. ad-hoc implementation to automate the release of the Sandbox versions.
Requirements
The release process should be automatically triggered on event of the tag placement. For the current version X.Y.Z, it should support both, a new version release i.e. X.Y.(Z+1) for fixes only and X.(Y+1).0 for features and fixes and a patch of the previous release i.e. X.(Y-1).(Z'+1) where X.(Y-1).Z' is the last version of the previous release.
The main branch should be synchronized with the latest version of the new release.
Each release has to have a dedicated branch which should be always up to date with the latest version for that release.
Additional operations such as updating
provisioning/version.txt
and version numbers in README.md files that are used for the walkthrough URL should be updated as well.The text was updated successfully, but these errors were encountered: