-
Notifications
You must be signed in to change notification settings - Fork 10
Add release tracker issue template #47
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
Open
fossedihelm
wants to merge
1
commit into
kubevirt:main
Choose a base branch
from
fossedihelm:tracker-template
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+82
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,82 @@ | ||
| --- | ||
| name: Release Tracker | ||
| about: Used to track the work which needs to be done every release cycle | ||
| title: '[1.XX] Release Tracker' | ||
| labels: sig/release | ||
| --- | ||
|
|
||
| <!-- | ||
| This template is used for tracking tasks that needs to be done in a release cycle. | ||
|
|
||
| The issue should be kept open for the entirety of the release cycle, until all tasks are completed. | ||
| --> | ||
|
|
||
| * Release Cycle: `KubeVirt 1.XX` | ||
| * [Release Timeline](https://github.com/kubevirt/sig-release/tree/main/releases/v1.XX) <!-- DON'T FORGET TO UPDATE THE LINK --> | ||
|
|
||
| ## Release tasks | ||
|
|
||
| ### 1. Before the start of the Release Cycle | ||
|
|
||
| - [ ] Captured feedback from previous release cycle retro and planned to incorporate it into the release cycle. | ||
| - [ ] Started planning the release schedule by opening a PR proposal, announcing it and requesting feedback via email | ||
| to [kubevirt-dev](https://groups.google.com/forum/#!forum/kubevirt-dev). | ||
| - [ ] Send the email to [kubevirt-dev](https://groups.google.com/forum/#!forum/kubevirt-dev) for schedule confirmation. | ||
|
|
||
| ### 2. First weeks of the release cycle up to Virtualization Enhancements Proposal Freeze | ||
|
|
||
| - [ ] Release schedule finalized. | ||
| - [ ] Announce schedule blog post. | ||
| - [ ] KubeVirt Alpha 0: | ||
| - [ ] Tag 1.XX.0-alpha.0. | ||
| - [ ] Start the provider for the latest k8s beta version, adding on-demand pre-submit. | ||
|
|
||
| **A week before Virtualization Enhancements Proposal Freeze:** | ||
|
|
||
| - [ ] Remind the community about Virtualization Enhancements Freeze. | ||
|
|
||
| ### 3. Enhancements freeze up to Release Code Freeze | ||
|
|
||
| - [ ] Tag 1.XX.0-beta.0: | ||
| - [ ] Prepare unconference for next version development cycle. | ||
| - [ ] Update common-instancetypes bundle in KubeVirt repo. | ||
| - [ ] Mandatory pre-submit lanes. | ||
| - [ ] Non-standard lanes (i.e. migrations, multus, ipv6) have been bumped by stakeholders. | ||
| - [ ] Begin casual observation of issues, CI signal, test flakes, and critical PRs. | ||
| - [ ] Notify SIGs and about upcoming Code Freeze Deadline. | ||
| - [ ] Bring exceptions to [kubevirt-dev](https://groups.google.com/forum/#!forum/kubevirt-dev). | ||
| - [ ] Feature Freeze: | ||
| - [ ] Review https://storage.googleapis.com/kubevirt-prow/reports/quarantined-tests/kubevirt/kubevirt/index.html | ||
| - [ ] Branch release-1.XX and tag v1.XX.0-rc.0 on release-1.XX. | ||
| - [ ] Generate api testdata for the new release and push them to main for backward compatibility testing. | ||
| - [ ] Gather scale & performance data. | ||
| - [ ] Unconference. | ||
| - [ ] Categorise release notes and create User Guide PR with /hold. | ||
| - [ ] Draft release highlights blog. | ||
fossedihelm marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - [ ] Test and production code stabilization: | ||
| - [ ] sig-compute | ||
| - [ ] sig-network | ||
| - [ ] sig-storage | ||
|
|
||
| ### 3. Around Release Day | ||
|
|
||
| - [ ] Collect SIG sign-offs on blog. | ||
| - [ ] Publish scale & performance data. | ||
|
|
||
| ### 4. Release Day | ||
|
|
||
| - [ ] Update release notes for any last-minute bugfixes. | ||
| - [ ] Tag v1.XX.0 on release-1.XX | ||
| - [ ] Ensure docs and blog PRs are approved. | ||
| - [ ] Send the email to [kubevirt-dev](https://groups.google.com/forum/#!forum/kubevirt-dev) for announcing. | ||
| - [ ] Publish/unhold release notes and blog. | ||
| - [ ] Promote through social media. | ||
| - | ||
| ### 5. Post Release | ||
|
|
||
| - [ ] Update KubeVirt Enhancements Tracking board link in [ROADMAP](https://github.com/kubevirt/sig-release/blob/main/ROADMAP.md) | ||
| - [ ] Update [label-approved-veps script](https://github.com/kubevirt/kubevirt/blob/main/.github/workflows/label_approved_veps.yaml) with the new `TARGET_PROJECT_URL` | ||
|
|
||
| ## Further comments | ||
|
|
||
| `NONE` | ||
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.
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.
At this point we could enforce merge of specific PRs only with a change to the tide configuration for kubevirt/kubevirt.
As an example kubernetes/kubernetes also does it by only allowing PRs with a specific milestone attached to merge: https://github.com/kubernetes/test-infra/pull/35171/files
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.
@xpivarc @fossedihelm @vladikr FYI
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.
See also: https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests
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.
This would be good. Thanks Daniel