public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio] [RFC] virtio 1.3 schedule
Date: Wed, 5 Apr 2023 15:23:10 -0400	[thread overview]
Message-ID: <20230405192310.GB676473@fedora> (raw)
In-Reply-To: <87edoyqvnu.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Wed, Apr 05, 2023 at 03:57:09PM +0200, Cornelia Huck wrote:
> 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.

Sounds good to me. If the date is earlier then it will be necessary to
scrutinize the list of features for 1.3 and think hard about which ones
fit, but freezing on July 1st sounds realistic to me.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2023-04-05 19:23 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 ` Stefan Hajnoczi [this message]
2023-04-07 11:24 ` [virtio-dev] " 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=20230405192310.GB676473@fedora \
    --to=stefanha@redhat.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