🚨VEP Authors 🚨 - find an assigned reviewer to your VEPs!

[Itamar Holder]

Hey all,

As mentioned in a previous mail, the number of VEPs proposed is dramatically increasing with every release. On the one hand, this is a blessed trend that is wonderful to see, as it means that the VEP process accomplishes its goals of being transparent, open and inclusive. On the other hand, it brings challenges because more VEPs require the participation of many community members in the review process.

With this huge volume of VEPs, we might not be able to track all of them in the current cycle due to insufficient review bandwidth. As written above, I consider this great news because it's a testament to how our community grows over time.

We've been discussing assigning explicit reviewers for VEPs to assess our community capacity for tracking which VEPs are realistic for a given release. For this reason, we added a "VEP Reviewer" column to the v1.9 enhancement tracking board.

Being an assigned VEP reviewer does not mean that the reviewer should be the only person to review VEP/implementation PRs. The assigned reviewer's responsibility is to be the one of the main reviewers and primarily to shepherd the VEP to success. For example, this means:

• To be one of the main reviewers for VEP / implementation PRs.
• To ensure the VEP author is aware of the deadlines.
• To raise a red flag if the VEP is blocked or likely to miss deadlines.
• To bring controversial topics to broad awareness in time.

We emphasize that VEPs without an assigned reviewer will not be able to be tracked for the upcoming release. As a VEP author, it is your responsibility to find a community member that is willing and capable to take this responsibility.

One of the best ways to find a reviewer for your VEP is to offer yourself as a VEP reviewer for others. This way we can help one another, as a community, to ensure we deliver as much high quality improvements as possible. You're welcome to respond to this mail by offering yourselves, or by using other mediums - public meetings, slack channel, etc.

Thank you very much for your cooperation,

Itamar.

[Itamar Holder]

I forgot to add a link to the v1.9 enhancement tracking github board.

So in case you don't have it:

https://github.com/orgs/kubevirt/projects/21

Another useful link is the v1.9 schedule, which can be found here:

https://github.com/kubevirt/sig-release/blob/main/releases/v1.9/schedule.md

[Aseef Imran]

Itamar,

Thanks for the heads-up. This is a big and important change. Have we already considered adding a section for this under the VEP template (for either the issue or the VEP itself?) This is help ensure we get the word out there.

[Zhenchao Liu]

On Wed, Apr 1, 2026 at 6:17 PM 'Itamar Holder' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

I forgot to add a link to the v1.9 enhancement tracking github board.

So in case you don't have it:

https://github.com/orgs/kubevirt/projects/21

Another useful link is the v1.9 schedule, which can be found here:

https://github.com/kubevirt/sig-release/blob/main/releases/v1.9/schedule.md

Hi Itamar,

As you know, graduating a feature requires a corresponding PR to update the VEP. Does this update also need to adhere to the VEP freeze date, or is the deadline specifically for new proposals?

Thanks,

Zhenchao

 

On Wed, 1 Apr 2026 at 13:15, Itamar Holder <iho...@redhat.com> wrote:

Hey all,

As mentioned in a previous mail, the number of VEPs proposed is dramatically increasing with every release. On the one hand, this is a blessed trend that is wonderful to see, as it means that the VEP process accomplishes its goals of being transparent, open and inclusive. On the other hand, it brings challenges because more VEPs require the participation of many community members in the review process.

With this huge volume of VEPs, we might not be able to track all of them in the current cycle due to insufficient review bandwidth. As written above, I consider this great news because it's a testament to how our community grows over time.

We've been discussing assigning explicit reviewers for VEPs to assess our community capacity for tracking which VEPs are realistic for a given release. For this reason, we added a "VEP Reviewer" column to the v1.9 enhancement tracking board.

Being an assigned VEP reviewer does not mean that the reviewer should be the only person to review VEP/implementation PRs. The assigned reviewer's responsibility is to be the one of the main reviewers and primarily to shepherd the VEP to success. For example, this means:

• To be one of the main reviewers for VEP / implementation PRs.
• To ensure the VEP author is aware of the deadlines.
• To raise a red flag if the VEP is blocked or likely to miss deadlines.
• To bring controversial topics to broad awareness in time.

We emphasize that VEPs without an assigned reviewer will not be able to be tracked for the upcoming release. As a VEP author, it is your responsibility to find a community member that is willing and capable to take this responsibility.

One of the best ways to find a reviewer for your VEP is to offer yourself as a VEP reviewer for others. This way we can help one another, as a community, to ensure we deliver as much high quality improvements as possible. You're welcome to respond to this mail by offering yourselves, or by using other mediums - public meetings, slack channel, etc.

Thank you very much for your cooperation,

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/CALpNySzqNYZMVLMNAH0P7EB0OTTTnuv-x-ddXSxVDgtoSM%2BoYw%40mail.gmail.com.

[Andrew Burden]

Hi Zengchao,

Does this update also need to adhere to the VEP freeze date, or is the deadline specifically for new proposals?

Good question. I also did not know but I asked this on your behalf on the Community call today and the answer is yes: the update to the VEP to cover the graduating feature needs to happen before the VEP deadline.
The newly migrated feature lifecycle doc has more information: https://github.com/kubevirt/enhancements/blob/main/docs/feature-lifecycle.md#feature-stages

Thanks!
Andrew

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