-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add Release Cheatsheet for Results #441
Conversation
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.
/kind documentation
Fixes #388 |
from the release branch. Refer to previous releases to confirm the expected format. | ||
1. Un-check the "This is a pre-release" checkbox since you're making a legit for-reals release! | ||
|
||
1. Publish the GitHub release once all notes are correct and in order. |
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.
We are missing a step to make the release "the default release". It's just another checkbox to fill.
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, we need to add this for a minor release.
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.
Phrased it below:
Mark the release as "the default release" if it's not a patch release or the patch release of the latest release.
Generally the documentation is good. Following it, I was able to do the v0.7.0 release. There was an issue with storing the release.yaml and version folders in the correct paths, so I had to fix those manually. I'll look into this later to determine if it's something we need to fix in the script or in the documentation. |
d313f50
to
74d8756
Compare
7282215
to
5cd0d89
Compare
Does this release cheatsheet work fine? @enarha |
The Cheatsheet is good and we can merge that PR. There is an issue which is a bug in some of the release scripts used. I've created #595 to handle it. |
/lgtm |
@avinal Let's approve this. It might fix the go coverage test that's failing if this gets merged. |
Yeah last release was successful, for now its good. We can iterate on this. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avinal 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
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes