Re: [virtio-comment] [RFC] virtio 1.3 schedule

["Michael S. Tsirkin" <mst@redhat.com>]

On Wed, Apr 05, 2023 at 03:57:09PM +0200, Cornelia Huck wrote:
> The virtio 1.2 spec has been released on July 1st, 2022, so I think we
> should come up with a plan for the 1.3 release. Given that it took us
> several months last time, we need to think about declaring freeze during
> (northern hemisphere) summer if we want to have a release ready before
> the end-of-year holiday season starts.
> 
> We have some things currently under discussion/review that we should
> still consider for 1.3:
> 
> - vq index etc. naming cleanup
> - admin vq
> - virtio-video
> - some things we deferred for 1.2 (see
>   https://github.com/oasis-tcs/virtio-spec/issues?q=is%3Aissue+is%3Aopen+label%3Adeferred-in-v1.2-csprd01)
> - other things that are not on my personal list (please mention whatever
>   you think is important)
> 
> Please also keep in mind that 1.3 will not be the last virtio release,
> and many projects like Linux or QEMU consider features stable and ready
> for inclusion once the spec has hit the git tree, but not neccessarily a
> virtio spec release.
> 
> That said, let me propose the following timeline:
> 
> - July 1st 2023: enter feature freeze; all proposed changes must at
>   least have an open github issue that refers to a proposal on-list
> - August 1st 2023: enter change freeze; everything needs to have been
>   voted upon (i.e. we can start with preparations for a release like
>   compiling the change log)
> - at the same time, fork virtio-next, which can be used for development
>   while we're working on the release
> - August/September 2023: prepare draft, initiate initial voting etc.

Hmm looks like you forgot a 30 day the public review period (or is that
included in the "etc"? ).  During this period we will likely receive
review comments which we have to address. Should the changes turn out to
be material, another public review period will be required.
Let's spell it out please.



> - by September/October 2023: have the final 1.3 spec ready, voted upon,
>   and released
> - virtio-next can be merged into mainline, and we continue with business
>   as usual
> 
> Thoughts? We might want to move things a tad earlier, but I don't think
> we should push the schedule out much further.