Exception Request for VEP #233 - Release Branch End-of-Life Policy

[Lee Yarwood]

Hi all,

I'd like to request a VEP freeze exception for VEP #233, Enforce
Release Branch End-of-Life Policy (owning SIG: release).

- Tracking issue: https://github.com/kubevirt/enhancements/issues/233
- VEP PR (rework): https://github.com/kubevirt/enhancements/pull/341
- Target: policy refinement for v1.10; this is a process/policy
change, no feature gate

1. Justification
PR #341 reworks the VEP to replace a hard 3-release EOL cutoff with a
dedicated release-branch maintainer governance model (preserving the
3-release full-support window, formalising extended
security/critical-fix support, and modelling maintainer-driven EOL on
OpenStack's stable-branch policy). It carries /lgtm from @EdDev and
near-approval from @fossedihelm; the remaining discussion (measuring
"active maintainers" / reusing the existing inactivity-based removal
for the approvals list) is a refinement on an otherwise agreed
direction.

2. Additional time requested
One week from the freeze date to fold in the final review feedback and merge.

3. Impact if not granted
This VEP formalises support behaviour the project already performs
informally. Slipping it prolongs the maintainer-fatigue problem it
addresses (core approvers spending a large share of review time on
backports) and leaves the support contract ambiguous for another
cycle, with no code risk to weigh against the delay.

Thanks,
Lee

[Edward Haas]

Hello,

Thank you @Lee Yarwood for investing in this.
I think this formalizes our intentions and preferences for handling older releases well.

As this proposal targets a policy and has no direct effect on the next release,
I do not think it needs to be bound to the VEP freeze timeline.

Thanks,
Edy.

--
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/CAPkJ9Dux5oc9SooAnmCB7REDGPx2wa1x3H9OiFprFZP0U-sdEg%40mail.gmail.com.

[Itamar Holder]

Hey Lee!

Since this VEP requires no implementation, we think we should tie it to any release and that the VEP should not be blocked by the VEP freeze.

Please feel free to continue the review process of this VEP.

Thanks!

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