-
Notifications
You must be signed in to change notification settings - Fork 17
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
Initial Release Instructions #223
Initial Release Instructions #223
Conversation
This is an initial guide on how to release the Shipwright operator. It provides guidance on how to create a release candidate build with GitHub actions, and adds release verification instructions to the OLM development guide. Future updates to this guide will include instructions on how to publish the new bundle to OperatorHub. Signed-off-by: Adam Kaplan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
||
Find the draft release. Edit the release as follows: | ||
|
||
- Add a leading `v` suffix to the generated tag and release name. Ex: `0.13.0-rc0` becomes `v0.13.0-rc0`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we avoid the need for this manual step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - I'll create an issue for follow-up.
/approve Self-approval (PR submitted by maintainer) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
This is an initial guide on how to release the Shipwright operator. It provides guidance on how to create a release candidate build with GitHub actions, and adds release verification instructions to the OLM development guide.
Future updates to this guide will include instructions on how to publish the new bundle to OperatorHub.
Related to #132
/kind documentation
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes