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] [virtio 1.3] Feature freeze has started
Date: Mon, 03 Jul 2023 14:41:32 +0200 [thread overview]
Message-ID: <874jml2mmb.fsf@redhat.com> (raw)
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
as part of the release process for the 1.3 version of the virtio spec,
we have now entered feature freeze. This means:
***
By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
to have at least a github issue open that is pointing to a patch (set)
on the list.
***
AFAICS, the list of features matching these criteria is the following:
https://github.com/oasis-tcs/virtio-spec/issues/173 ("virtio-net:
support inner header hash")
* this looks very close, with voting likely to start in the next
couple of days
https://github.com/oasis-tcs/virtio-spec/issues/167 ("Support
transitional device for PCIe VF")
* I have not followed that one in detail, but it has been stated that
this one should also be ready soon -- can people please confirm that
this will be ready for inclusion in July?
https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
negotiated.")
* Can someone please check the status of this? Looks like a patch is
available, but no progress for a long time? Is this maybe interacting
with the inner header hash feature?
Any others that I have missed?
I'd like to wrap this up in July; not a real problem if we spill over
a couple of days into August, but I'd really like to avoid delaying the
process for too much (it will take long enough already.)
virtio 1.3 timeline:
Development
July 3rd: feature freeze (github issue <-- we are here
and change on list)
August 1st: change freeze (all voted
upon)
virtio-next development branch opens
August: prepare draft
August 31st (latest): draft voted upon by TC
September: public review period
October: addtl public review period, if needed
October (November): 1.3 released
merge virtio-next development branch
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-07-03 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:41 Cornelia Huck [this message]
2023-07-21 13:08 ` [virtio-comment] Re: [virtio-dev] [virtio 1.3] Feature freeze has started Cornelia Huck
2023-07-21 14:21 ` 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=874jml2mmb.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).