Adding pre-flight release checklist #30
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kubevirt-bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
aburdenthehand
force-pushed
the
pre-release-checklist
branch
2 times, most recently
from
b4346b3
to
1fcf0a9
Compare
…o preparing the tag (release notes, blogs, perf data, etc). Also adding a subset of these to the 1.5 schedule so that they are visible in our weekly release check-in in the community meeting. Signed-off-by: Andrew Burden <[email protected]>
aburdenthehand
force-pushed
the
pre-release-checklist
branch
from
1fcf0a9
to
f6e82f0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist includes tasks in addition to preparing the tag (release notes, blogs, perf data, etc).
Also adding a subset of these to the 1.5 schedule so that they are visible in our weekly release check-in in the community meeting.
Rationale: We only do 3 releases a year so it is easy to forget some of these things, especially depending on the time of year. This way we have an evolving set of tasks and an indication when we should be initiating and completing them for the smoothest of smooth releases.
Release note: