VEP 233: Set v1.9.0-beta.0 deadline for dead branch archival#305
Open
lyarwood wants to merge 1 commit into
Open
VEP 233: Set v1.9.0-beta.0 deadline for dead branch archival#305lyarwood wants to merge 1 commit into
lyarwood wants to merge 1 commit into
Conversation
kubevirt-bot
added
the
dco-signoff: no
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Replace "immediately" with a concrete deadline of v1.9.0-beta.0 for archiving release-0.4 through release-0.57, giving downstream users and vendors a grace period to react before branches are locked. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Lee Yarwood <lyarwood@redhat.com>
lyarwood
force-pushed
the
vep-233-archive-deadline
branch
from
0e198a9 to
a782332
Compare
kubevirt-bot
added
dco-signoff: yes
Member
Author
|
/cc @dhiller Hope you don't mind but I'm going to propose v1.9.0 beta.0 as the deadline for the initial dead release branch clean up now just to ensure downstream vendors get a chance to respond. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
VEP Metadata
Tracking issue: #233
SIG label: /sig release
What this PR does
Sets a concrete deadline of v1.9.0-beta.0 (May 21, 2026) for archiving the dead release branches (release-0.4 through release-0.57), replacing the previous "immediately" language in the transition plan.
This gives downstream users and vendors a grace period to react before the branches are locked via kubevirt/project-infra#5041.
Special notes for your reviewer
This aligns with the announcement being sent to kubevirt-dev@googlegroups.com.