KubeVirt v1.9 development cycle
Vladik Romanovsky
Hi everyone,
The v1.9 development cycle will start soon. Here is the proposed release schedule
Here are the key dates:
- April 30 — VEP Freeze (and Alpha 0)
- May 21 — Beta 0
- June 24 — Code Freeze (RC 0)
- July 22 — GA release
As we enter the design phase, the community’s focus should shift towards reviewing VEPs (and fixing critical bugs, of course) until the VEP freeze on April 30th.
VEP Tracker for v1.9
We’ve set up a project board to track VEP progress for this release: https://github.com/orgs/kubevirt/projects/21
The v1.9 tracker includes several new fields that are automatically populated:
- Proposal PRs — list of the proposal pull requests
- Implementation PRs — list of the implementation pull requests
- Agent Urgency — RED/YELLOW/GREEN status indicating how much attention a VEP needs
- Agent Comment — a brief assessment of the VEP’s status and likelihood of landing in time
These fields will start getting filled once the cycle begins. If you notice any inconsistencies in the data, please report them.
For reference, here’s what the v1.8 tracker looked like: https://github.com/orgs/kubevirt/projects/19/views/7
These fields are being populated by the vep-police-agent, a project Itamar Holder and I have been developing so far. It’s an agent designed to help us manage VEPs throughout the development cycle. It automatically discovers VEPs from issues and PRs in the github.com/kubevirt/enhancements repo, links them to their proposal and implementation PRs, monitors compliance (SIG sign-offs, template completeness), tracks deadlines against the release schedule, flags inactive or at-risk VEPs, and writes its findings back to the project board. It also sends alerts to the #kubevirt-vep-agent-alerts channel on the CNCF Slack.
The goal is to significantly reduce the manual effort needed for tracking VEP progress and give the community clear visibility.
The project is still in early stages. There is a lot of room for new ideas and improvements. We plan to eventually move it under the kubevirt organization on GitHub. Feedback and contributions are more than welcome.
Thanks,
Vladik