From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: "virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
"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: Fri, 30 Jun 2023 10:47:33 +0200 [thread overview]
Message-ID: <877crl49qy.fsf@redhat.com> (raw)
In-Reply-To: <20230629153345-mutt-send-email-mst@kernel.org>
On Thu, Jun 29 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Jun 29, 2023 at 05:41:34PM +0000, Parav Pandit wrote:
>> Hi Cornelia, Michael,
>>
>> > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
>> > open.org> On Behalf Of Cornelia Huck
>> > Sent: Wednesday, April 12, 2023 12:17 PM
>>
>> > >> - 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.
>> >
>> > Yeah, that's what I meant with "etc"... let's make this:
>> >
>> > - August 2023: prepare draft, aim to have it ready and voted upon by
>> > August 31 the latest (preferrably earlier)
>> > - September 2023: public review period (30 days)
>> > - October 2023: another public review period, if needed; otherwise, get
>> > comittee specification ready and voted upon
>> > - October (maybe November, if we're running late) 2023: virtio 1.3
>> > released
>> >
>> > The most important dates are feature freeze on Jul 1 and change freeze on Aug
>> > 1, I guess; for the rest, we depend on whether people are out on PTO, which
>> > kind of feedback we get, etc. -- but as long as we release
>> > 1.3 in 2023, I'll be happy enough.
>>
>> We have two extension features that has gone through several reviews and are in advance stage (and also late) for 1.3. :)
>>
>> 1. inner hash v19, rolling to v20 anytime this week. 1 Patch.
>> [1] https://lists.oasis-open.org/archives/virtio-comment/202306/msg00490.html
>>
>> 2. first user of aq for legacy access at v7.
>> 2 patches. First 2 are Fixes.
>> [2] https://lists.oasis-open.org/archives/virtio-comment/202306/msg00491.html
>>
>> Both need few more days of review and vote.
>> Shall we please have few days in July for them so that it can be part of 1.3?
>> or whole July is needed to prepare the draft spec?
>
> I think it's not too bad, projects that do releases every couple of
> months can afford to be strict, we do them ones a year and a half
> it makes sense to be flexible.
Yes, my only concern is to avoid slipping too badly -- and the "feature
freeze" period was actually intended to give us some time to wrap up
outstanding features.
For the inner header hash, I see there's already an issue (#173), so
it's good. I have not followed the aq legacy access feature -- if
everyone agrees that we should be able to vote on it in July, we should
have an issue for it as well (I cannot find one just by looking at
titles.)
Any other features that people are aware of?
---------------------------------------------------------------------
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-06-30 8:47 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 ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
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 [this message]
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=877crl49qy.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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).