From: Parav Pandit <parav@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Subject: [virtio-dev] RE: [virtio-comment] [RFC] virtio 1.3 schedule
Date: Wed, 5 Apr 2023 14:05:59 +0000 [thread overview]
Message-ID: <PH0PR12MB54818CAC4966B180BAB8808ADC909@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87edoyqvnu.fsf@redhat.com>
Hi Cornelia,
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Cornelia Huck
> Sent: Wednesday, April 5, 2023 9:57 AM
>
> 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 included transitional VF device support to the list whose proposal is already in progress.
It has matching github issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-04-05 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:57 [virtio-dev] [RFC] virtio 1.3 schedule Cornelia Huck
2023-04-05 14:05 ` Parav Pandit [this message]
2023-04-05 19:23 ` [virtio-dev] Re: [virtio] " Stefan Hajnoczi
2023-04-07 11:24 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-12 16:16 ` Cornelia Huck
2023-06-29 17:41 ` [virtio-dev] " Parav Pandit
2023-06-29 19:35 ` [virtio-dev] " Michael S. Tsirkin
2023-06-30 8:47 ` Cornelia Huck
2023-06-30 8:55 ` Michael S. Tsirkin
2023-06-30 11:14 ` [virtio-dev] " 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=PH0PR12MB54818CAC4966B180BAB8808ADC909@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=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).