On Tue, 9 Jun 2026 at 19:00, Stefan Hajnoczi <[email protected]> wrote: > I'm not sure if anyone brought up this topic on qemu-devel and with > Michael before. As I mentioned in my reply, there are ways to avoid > blocking vhost-user spec changes when qemu.git is frozen: > > The simplest approach is to keep merging vhost-user.rst changes during > freeze since it does not jeopardize the release or introduce > instability.
I'm not enthusiastic about having "this one document is an exception to our freeze and release process". Because it is only documentation, it is in the same "we can be relatively relaxed about allowing in documentation changes" boat as most of the rest of the docs. But docs changes can break the build (e.g. if you mess up a rST syntax thing), so as we get closer to the final release we are going to get more strict about "is this change really necessary or can it wait a few weeks?", and they must at a minimum continue to obey the "no changes of any kind between the last RC and the final release" rule. And definitely if a patchseries has both QEMU code changes and documentation updates then that is going to not get applied during freeze if the code changes don't follow the freeze rules. "There are going to be three well-advertised periods every year of about three weeks in length when you can't get an update into the spec document" doesn't seem particularly unworkable to me. But if following QEMU's release process is too awkward for this document, then I think the right thing is to make it an independent document, like the virtio spec. thanks -- PMM
