From: Cornelia Huck <cohuck@redhat.com>
To: virtio@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: [virtio-comment] [RFC] virtio 1.3 schedule
Date: Wed, 05 Apr 2023 15:57:09 +0200 [thread overview]
Message-ID: <87edoyqvnu.fsf@redhat.com> (raw)
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.
- 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.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next reply other threads:[~2023-04-05 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:57 Cornelia Huck [this message]
2023-04-05 14:05 ` [virtio-comment] [RFC] virtio 1.3 schedule Parav Pandit
2023-04-05 19:23 ` [virtio-comment] Re: [virtio] " Stefan Hajnoczi
2023-04-07 11:24 ` [virtio-comment] " Michael S. Tsirkin
2023-04-12 16:16 ` Cornelia Huck
2023-06-29 17:41 ` Parav Pandit
2023-06-29 19:35 ` Michael S. Tsirkin
2023-06-30 8:47 ` Cornelia Huck
2023-06-30 8:55 ` Michael S. Tsirkin
2023-06-30 11:14 ` Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edoyqvnu.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).