Re: [virtio-comment] [RFC] virtio 1.3 schedule

["Michael S. Tsirkin" <mst@redhat.com>]

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.

-- 
MST


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/