OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [virtio-comment] Plans for releasing a VIRTIO 1.2 spec


On Montag, 20. Dezember 2021 13:47:03 CET Cornelia Huck wrote:
> We are due (or rather overdue) for a new release of the VIRTIO spec. As
> doing a release takes some time, we need to tie things up soon (remember
> that there will also be a next revision for changes that don't make the
> cut.)
> 
> We propose to declare a freeze on changes starting January 25th, 2022 (no
> new non-editorial changes committed). This would mean that any ballot
> needs to conclude on January 24th the latest (and therefore has to be
> opened before January 17th). Any change that you want to see included in
> 1.2 has to reach enough consensus to open a ballot in early January 2022.
> 
> Next steps would be creating a Comittee Specification Draft (and voting
> on it), putting it out for review, and then creating (and voting on) a
> Comittee Specification, hopefully before the end of March 2022.
> 
> To reiterate, anything that should be included in VIRTIO 1.2 needs to
> have a ballot started
> 
>               *before January 17th, 2022*
> 
> at the very latest (preferably earlier).

As holidays are starting this week, that realistically means a window of about 
just one or two weeks, for both bringing a discussion eventually to its spec 
commit, as well as concluding its subsequent ballot.

Maybe it's just me, but considering that the last virtio revision was 3 years 
ago, that sounds like a sudden hammer fall to me.

> This should give us enough time to tie up most proposals currently
> actively discussed. Again, remember that anything that is late will
> simply make it into the next release instead.

Which will be when approximately?

> Please let us know if you have any concerns.
> 
> The VIRTIO TC Chairs

Spec issues that won't make it through within this narrow time window would 
not suffer under any negative consequences in form of reluctance for their 
actual implementation patches on Linux kernel / QEMU side, would they?

Best regards,
Christian Schoenebeck




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]