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] Reminder: Feature freeze coming up on July 1st
Date: Mon, 05 Jun 2023 19:09:31 +0200 [thread overview]
Message-ID: <87edmp4z04.fsf@redhat.com> (raw)
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
we'll soon start the process of getting version 1.3 of the virtio spec
released. As a first step, we'll enter feature freeze on July 1st. This
means:
***
By July 1st, 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.
***
This should hopefully give us enough time to conclude voting for those
features before we enter change freeze on August 1st.
virtio 1.3 timeline:
Development <-- we are here
July 1st: feature freeze (github issue
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/
WARNING: multiple messages have this Message-ID (diff)
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-dev] [virtio 1.3] Reminder: Feature freeze coming up on July 1st
Date: Mon, 05 Jun 2023 19:09:31 +0200 [thread overview]
Message-ID: <87edmp4z04.fsf@redhat.com> (raw)
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
we'll soon start the process of getting version 1.3 of the virtio spec
released. As a first step, we'll enter feature freeze on July 1st. This
means:
***
By July 1st, 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.
***
This should hopefully give us enough time to conclude voting for those
features before we enter change freeze on August 1st.
virtio 1.3 timeline:
Development <-- we are here
July 1st: feature freeze (github issue
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
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2023-06-05 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 17:09 Cornelia Huck [this message]
2023-06-05 17:09 ` [virtio-dev] [virtio 1.3] Reminder: Feature freeze coming up on July 1st Cornelia Huck
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=87edmp4z04.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.