Add release tracker issue template

[fossedihelm]

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]

/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.

[Sreeja1725]

@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]

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]

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]

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

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

[dhiller]

@xpivarc @fossedihelm @vladikr FYI

[dhiller]

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

[fossedihelm]

This would be good. Thanks Daniel