Exception request for VEP 76, 256, and 222

[Felix Matouschek]

Hi everyone,

I would like to request an exception for VEP 76, VEP 256, and VEP 222.

The bulk of the PRs for these VEPs have already been reviewed and LGTM'd/approved. We are currently waiting on CI.

There are two remaining follow-up PRs that are ready but cannot be merged yet, as they are dependent on the approved PRs currently waiting on CI.

Thanks, Felix

VEPs:

https://github.com/kubevirt/enhancements/issues/76
https://github.com/kubevirt/enhancements/issues/256
https://github.com/kubevirt/enhancements/issues/222

Remaining follow-up PRs:
https://github.com/kubevirt/kubevirt/pull/18065
https://github.com/kubevirt/kubevirt/pull/18067

[Itamar Holder]

Hey Felix,

From my POV PRs that were LGTMed+approved before the freeze and weren't merged only due to CI pressure get an automatic pass.

For the other PRs, I'll let people that were more involved with these VEPs share their thoughts.

BR,

Itamar.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/ce4dee35-8495-451e-96fd-f30737737b1en%40googlegroups.com.

[Luboslav Pivarc]

Hi Felix,

Please consider writing separate emails for each VEP next time, it keeps things clearly separated. Please also include all the requested points, as written in https://github.com/kubevirt/enhancements#exceptions  ref:
"""
Justification for exception
Additional time period that is required
In case of exception not being granted, what is the impact? (Think about graduation, maturity of the feature, user impact, etc.)
"""

VEP 76

This seems to be done, correct?

VEP 222

1. Please update the tracker with relevant PRs.

2. The PRs I could track myself seem not to be merged. We should consider this feature to have missed the 1.9 release.

VEP 256

This seems to be done, correct?

-Lubo

To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CALpNySzDmCodCpeMon9UPzrDs4FLYMekLm5CbfkXNpbyb5BnhQ%40mail.gmail.com.

[Felix Matouschek]

Hi Lubo,

On Wed, Jul 1, 2026 at 10:53 PM Luboslav Pivarc <lpi...@redhat.com> wrote:

Hi Felix,

Please consider writing separate emails for each VEP next time, it keeps things clearly separated. Please also include all the requested points, as written in https://github.com/kubevirt/enhancements#exceptions  ref:
"""
Justification for exception
Additional time period that is required
In case of exception not being granted, what is the impact? (Think about graduation, maturity of the feature, user impact, etc.)
"""

Right, will do next time.

 

VEP 76

This seems to be done, correct?

Yes, it's done.

 

VEP 222

1. Please update the tracker with relevant PRs.

2. The PRs I could track myself seem not to be merged. We should consider this feature to have missed the 1.9 release.

1. Right, I updated the tracker issue.

2. Yes, the two PRs still haven't been merged. That is mainly due to very late reviews, long reviewer response times and CI flakes.

The PRs were posted almost a month prior to the code freeze, which makes it quite disappointing that they missed the 1.9 release.

 

VEP 256

This seems to be done, correct?

Yes, this one is done too.