Release 1.7 - status and backporting

[Luboslav Pivarc]

Hi everyone,

As you could notice the branching happened on 29th Oct (Wednesday) as per plan and as of today we also have CI for the stable branch. This means we are moving into the stabilization phase and the next milestone is Release candidate on 12th November. I noticed that CI was and still is overloaded and things that got approve ahead of branching still didn’t get merged, for example https://github.com/kubevirt/kubevirt/pull/15970 (as of writing). Therefore, exceptionally if you are the author of such PR and it isn’t necessarily a destabilizing feature, please open a backport PR, let's have a hard deadline at the end of next week. If you are not sure about what could be backported, please reach out to me here or personally. Finally, if any tracked VEPs (or features) fell short of their completion criteria due to minor oversights, please don't hesitate to reach out.

One VEP that asked for an exception and was granted, is the https://github.com/kubevirt/enhancements/issues/69. cc @Sreeja Varnam IN 

I want to thank everyone who contributed to this release and ask for help to push this release across the finish line in the best condition possible. If you can help out with quarantine tests https://storage.googleapis.com/kubevirt-prow/reports/quarantined-tests/kubevirt/kubevirt/index.html or flaky test https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days.html, please do so.

Reminder, next Tuesday we meet at un-conference, a great place to start your work/discussion on features for 1.8.

Have a nice weekend,

Lubo (xpivarc)

[Daniel Hiller]

Hey all,

we just had a discussion in today SIG CI meeting on how we would be able to steer the merging of PRs during code freeze - one possibility that came up was the introduction of something similar to what K8S does [1], i.e. letting only PRs with a release milestone set getting considered for merging by tide, while also avoiding to halt those PRs since it might stop an entire batch. More details in the CI meeting notes, should be a discussion worthy for the unconference.

[1]: https://github.com/kubernetes/test-infra/commit/bbbd7793a0aaa6eecc4dadcc91e6a230e1530f9b

--
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/CAFTR0GVpSDf7My3kmbG2p9KKzB4ud1R5-rd7oEme4MnE7D0oPQ%40mail.gmail.com.

--

-- 

Best,

Daniel

[Noam Assouline]

Hi everyone,
I'm writing to request an exception to merge the backport of the following PR into v1.7: https://github.com/kubevirt/kubevirt/pull/15409
This is important for the UI team as they wish to include it in the upcoming 4.21 release to provide clearer VM Snapshot indication descriptions for users.
As noted here, this is not a destabilizing feature. it simply adds a new status field (SourceIndications) for the new descriptions and marks the legacy field as deprecated.
The original PR is fully approved, and the backport PR for release-1.7 has been created.
Original PR: https://github.com/kubevirt/kubevirt/pull/15409
Backport PR: hhttps://github.com/kubevirt/kubevirt/pull/16033
Given the low risk and high importance for the UI team, we'd greatly appreciate getting this merged for 1.7.

Noam

[Noam Assouline]

Hi everyone,

I am requesting an exception to backport the following PR into the v1.7 release:
Original PR: https://github.com/kubevirt/kubevirt/pull/15409 - Merged
Backport PR: https://github.com/kubevirt/kubevirt/pull/16033

This PR provides richer information in vm snapshot status, which significantly improves the user experience and feedback of the snapshot quality for end-users, both for the CLI and other vendor solutions built on KubeVirt.
As noted, this is not a destabilizing feature. The change is minimalistic and contained, and it does not alter any technical logic.
The original PR was open for a while and, due to some technicalities, unfortunately missed the branching deadline.

Given the current delay with tagging the version, this feels like a great opportunity to get this low-risk improvement into the 1.7 release.

Thanks,
Noam

On Friday, October 31, 2025 at 2:59:06 PM UTC+2 Luboslav Pivarc wrote:

[Shelly Kagan]

Hi everyone,

I'd like to second Noam's request for the exception. The PR offers significant value to users by providing purely informational enhancements that are not disruptive. It would be highly beneficial to include this in the current release rather than postponing it to the next version, especially since it presents no risk to stability.

Cheers,
Shelly

Shelly Kagan

Senior Software Engineer

Red Hat

--

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/91032578-cd58-452a-a946-8732bcdd4bb7n%40googlegroups.com.

[Michael Henriksen]

On Wed, Nov 5, 2025 at 5:15 AM 'Shelly Kagan' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

Hi everyone,

I'd like to second Noam's request for the exception. The PR offers significant value to users by providing purely informational enhancements that are not disruptive. It would be highly beneficial to include this in the current release rather than postponing it to the next version, especially since it presents no risk to stability.

+1 to https://github.com/kubevirt/kubevirt/pull/16033 

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

[Luboslav Pivarc]

Hi @Noam Assouline ,

With Michael blessing (SIG Storage) I am keen to bless this exeptionally as well. The change itself seems more like fix of past API design flaw. 
BUT for future please ensure important changes are reviewed in time or they request exception not after deadline (In this case by SIG Storage).

-Lubo

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

[Noam Assouline]

Thank you @Luboslav Pivarc, I really appreciate you and Michael making this exception for us.

Your feedback on the process is definitely noted.

Thanks again for all the help,
Noam