Add release tracker issue template #47

fossedihelm · 2025-07-23T10:07:14Z

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Design: A design document was considered and is present (link) or not required
PR: The PR description is expressive enough and will help future contributors
Code: Write code that humans can understand and Keep it simple
Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
Upgrade: Impact of this change on upgrade flows was considered and addressed if required
Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
Community: Announcement to kubevirt-dev was considered

Release note:

none

fossedihelm · 2025-07-23T10:07:39Z

/cc @xpivarc @aburdenthehand @lyarwood @vladikr @iholder101 @dhiller

dhiller

I'd appreciate having the lane bump as a separate action item.

Also the stabilization should be done per SIG, probably a check as reminder will help.

.github/ISSUE_TEMPLATE/release-tracker.md

Sreeja1725 · 2025-07-23T14:47:51Z

@fossedihelm we can also add an action-item to create a new release directory under api testdata during the code-freeze.
By following these steps - https://github.com/kubevirt/kubevirt/tree/main/staging/src/kubevirt.io/api/apitesting/testdata#populating-data-for-each-release

dhiller

We should probably name the sigs that own the action items. WDYT?

dhiller

/lgtm

Thank you @fossedihelm

fossedihelm · 2025-07-28T12:32:27Z

We should probably name the sigs that own the action items. WDYT?

@dhiller We can, but still not sure how, trying to keep the template lightweight. WDYT about a followup?

dhiller · 2025-07-28T13:04:43Z

We should probably name the sigs that own the action items. WDYT?

@dhiller We can, but still not sure how, trying to keep the template lightweight. WDYT about a followup?

Agree, let's capture that thought in a follow up and then we should be good to go.

/lgtm

dhiller

/approve

/hold to let others chime in, feel free to remove when we are good to go with this.

kubevirt-bot · 2025-07-31T13:23:47Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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:

~~OWNERS~~ [dhiller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

dhiller · 2025-08-01T09:38:04Z

.github/ISSUE_TEMPLATE/release-tracker.md

+    - [ ] 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.


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

@xpivarc @fossedihelm @vladikr FYI

See also: https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests

This would be good. Thanks Daniel

vladikr · 2025-10-16T23:49:25Z

Do we still need the hold?

fossedihelm · 2025-10-17T02:35:56Z

@vladikr I would like to observe the manual created one for 1.7 #51 at least until the Code freeze, so that we can integrate the missing parts.
Thank you

kubevirt-bot · 2025-10-30T07:03:31Z

New changes are detected. LGTM label has been removed.

Signed-off-by: fossedihelm <[email protected]>

fossedihelm · 2025-10-30T07:38:16Z

I made the changes performed during release cycle 1.7.

aburdenthehand

Great stuff @fossedihelm
I have some feedback but this looks solid and very helpful.
Thanks for putting this together and apologies for the delay in review from my end.

aburdenthehand · 2025-12-01T17:38:26Z

.github/ISSUE_TEMPLATE/release-tracker.md

+
+### 1. Before the start of the Release Cycle
+
+- [ ] Captured feedback from the previous release cycle retro and planned to incorporate it into the release cycle.


When/where does this happen? I know some of the unconf's have had a retro but they're always prior to the release itself.

aburdenthehand · 2025-12-04T09:26:19Z

.github/ISSUE_TEMPLATE/release-tracker.md

+### 2. First weeks of the release cycle up to Virtualization Enhancements Proposal Freeze
+
+- [ ] Release schedule finalized.
+  - [ ] Announce schedule blog post.


Suggested change

- [ ] Announce schedule blog post.

- [ ] Announce schedule.

Better communicating over mailing list and social media accounts but we can leave this open.

aburdenthehand · 2025-12-04T09:28:21Z

.github/ISSUE_TEMPLATE/release-tracker.md

+
+**A week before Virtualization Enhancements Proposal Freeze:**
+
+- [ ] Remind the community about Virtualization Enhancements Freeze.


This should probably be part of the second point actually. At the moment I think it's necessary to highlight the VEP freeze date on a weekly basis.

aburdenthehand · 2025-12-04T09:31:20Z

.github/ISSUE_TEMPLATE/release-tracker.md

+- [ ] Begin casual observation of issues, CI signal, test flakes, and critical PRs.
+- [ ] Notify SIGs about upcoming Code Freeze Deadline.
+- [ ] Bring exceptions to [kubevirt-dev](https://groups.google.com/forum/#!forum/kubevirt-dev).
+- [ ] Code Freeze:


This is quite a big list. Should we split Code Freeze and After Code Freeze into their own dedicated sections?

kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Jul 23, 2025

kubevirt-bot requested review from dhiller and xpivarc July 23, 2025 10:07

kubevirt-bot added the size/M label Jul 23, 2025

kubevirt-bot requested review from aburdenthehand, iholder101, lyarwood and vladikr July 23, 2025 10:07

dhiller reviewed Jul 23, 2025

View reviewed changes

.github/ISSUE_TEMPLATE/release-tracker.md Outdated Show resolved Hide resolved

.github/ISSUE_TEMPLATE/release-tracker.md Outdated Show resolved Hide resolved

fossedihelm force-pushed the tracker-template branch from e618f51 to f18527a Compare July 23, 2025 12:31

dhiller reviewed Jul 24, 2025

View reviewed changes

dhiller approved these changes Jul 28, 2025

View reviewed changes

kubevirt-bot assigned dhiller Jul 28, 2025

kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 28, 2025

fossedihelm force-pushed the tracker-template branch from f18527a to bc3a481 Compare July 28, 2025 13:00

kubevirt-bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 28, 2025

kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 28, 2025

fossedihelm force-pushed the tracker-template branch from bc3a481 to a26d375 Compare July 31, 2025 09:43

kubevirt-bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2025

fossedihelm force-pushed the tracker-template branch 2 times, most recently from 9b42163 to ea80d52 Compare July 31, 2025 12:03

dhiller approved these changes Jul 31, 2025

View reviewed changes

kubevirt-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jul 31, 2025

kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2025

dhiller reviewed Aug 1, 2025

View reviewed changes

fossedihelm mentioned this pull request Sep 11, 2025

kubevirt,presubmits: Introduce the k8s-1.34 presubmit jobs to always run against PRs kubevirt/project-infra#4358

Merged

8 tasks

fossedihelm force-pushed the tracker-template branch from ea80d52 to 15c9185 Compare October 30, 2025 07:03

kubevirt-bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 30, 2025

fossedihelm force-pushed the tracker-template branch from 15c9185 to 8650bd6 Compare October 30, 2025 07:06

Add release tracker issue template

c779fa2

Signed-off-by: fossedihelm <[email protected]>

fossedihelm force-pushed the tracker-template branch from 8650bd6 to c779fa2 Compare October 30, 2025 07:10

aburdenthehand reviewed Dec 4, 2025

View reviewed changes


		### 1. Before the start of the Release Cycle

		- [ ] Captured feedback from the previous release cycle retro and planned to incorporate it into the release cycle.


		A week before Virtualization Enhancements Proposal Freeze:

		- [ ] Remind the community about Virtualization Enhancements Freeze.

Add release tracker issue template #47

Are you sure you want to change the base?

Add release tracker issue template #47

Uh oh!

Conversation

fossedihelm commented Jul 23, 2025

Uh oh!

fossedihelm commented Jul 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dhiller left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Sreeja1725 commented Jul 23, 2025

Uh oh!

dhiller left a comment

Choose a reason for hiding this comment

Uh oh!

dhiller left a comment

Choose a reason for hiding this comment

Uh oh!

fossedihelm commented Jul 28, 2025

Uh oh!

dhiller commented Jul 28, 2025

Uh oh!

dhiller left a comment

Choose a reason for hiding this comment

Uh oh!

kubevirt-bot commented Jul 31, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vladikr commented Oct 16, 2025

Uh oh!

fossedihelm commented Oct 17, 2025

Uh oh!

kubevirt-bot commented Oct 30, 2025

Uh oh!

fossedihelm commented Oct 30, 2025

Uh oh!

aburdenthehand left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

fossedihelm commented Jul 23, 2025 •

edited

Loading