Skip to content

VEP-111: postpone graduation to v1.10#275

Open
orelmisan wants to merge 1 commit intokubevirt:mainfrom
orelmisan:update-111
Open

VEP-111: postpone graduation to v1.10#275
orelmisan wants to merge 1 commit intokubevirt:mainfrom
orelmisan:update-111

Conversation

@orelmisan
Copy link
Copy Markdown
Member

@orelmisan orelmisan commented Apr 19, 2026

VEP Metadata

Tracking issue: #111
SIG label: /sig network

What this PR does

This feature cannot graduate to GA before its prerequisite [1] graduates to GA. Since the prerequisite is graduating to Beta in v1.9, the earliest this feature can reach GA is v1.10.

[1] #141

Special notes for your reviewer

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Apr 19, 2026
@orelmisan
Copy link
Copy Markdown
Member Author

/cc @EdDev

Copy link
Copy Markdown
Member

@EdDev EdDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

Not sure if it is a must to update the prediction on the VEP itself, but it surely cannot hurt.

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 20, 2026
Copy link
Copy Markdown
Member

@xpivarc xpivarc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/hold

## Graduation

In case no major issues will be reported, the feature gate will be graduated in v1.9.
In case no major issues will be reported, the feature gate will be graduated in v1.10.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you write that this is dependent on other VEP?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 20, 2026
@kubevirt-bot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xpivarc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 20, 2026
This feature cannot graduate to GA before its prerequisite [1]
graduates to GA. Since the prerequisite is graduating to Beta in
v1.9, the earliest this feature can reach GA is v1.10.

[1] kubevirt#141

Signed-off-by: Orel Misan <omisan@redhat.com>
@kubevirt-bot kubevirt-bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 21, 2026
@orelmisan
Copy link
Copy Markdown
Member Author

Change: Addressed @xpivarc's comment.

@orelmisan orelmisan requested review from EdDev and xpivarc April 21, 2026 07:41
@orelmisan
Copy link
Copy Markdown
Member Author

@EdDev @xpivarc can we move forward with this PR?

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. 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. sig/network size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants