Should the TC approve CSD05 Working Draft as a Committee Specification Draft, and submit the draft for public review as CSPRD05 Committee Specification Public Review Draft?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
A Full Majority Vote is required for this motion to pass -
Abstentions are not counted.
I move that:
1. The TC approves virtio 1.0 Working Draft CSD05
and all associated artifacts packaged together in
https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/56740/virtio-v1.0-csd05.zip
as a Committee Specification Draft and designate the TeX version
of the document as authoritative.
2. The TC approves that same Committee Specification Draft
(repackaged as Committee Specification Public Review Draft 05:
Virtual I/O Device (VIRTIO) Version 1.0 CSPRD05) and all
associated artifacts packaged together in
https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/56741/virtio-v1.0-csprd05.zip
be released for 15 day public review.
The changes made since Virtio 1.0 CS03 are identified in
files virtio-v1.0-csprd05-diff.pdf and/or
virtio-v1.0-csprd05-diff.html within this package.
3. The TC accepts the following changes to the specification,
(already included in the above drafts):
------------------------------------------------------------------------
r545 | mstsirkin | 2015-10-21 17:19:35 +0300 (Wed, 21 Oct 2015) | 32 lines
Revert: makediff: cleanup using begingroup/endgroup
This reverts commit
commit ef519a86f046d1be22f82f32d845653a850c21dd
Author: mstsirkin
Date: Thu Jun 26 16:50:13 2014 +0000
makediff: cleanup using begingroup/endgroup
This seemed like a good idea originally: replace perl hacks with
tex hacks. However adding begingroup and endgroup within macros
used by latex-diff breaks its assumption that these are low level
tex and can be used in arbitrary situations, e.g. cross the
boundaries of environments, use mis-matching begin and end
instructions (DIFaddbegin with DIFaddendFL), etc.
Let's go back to the original work-around:
commit b665b3165b454b98c782617e37a128b53b56c89c
Author: mstsirkin
Date: Thu Jun 26 12:34:38 2014 +0000
work around xetex bug
Too many color directives produce corrupted output
and this warning:
WARNING ** Color stack overflow. Just ignore.
Use script to reduce # of these directives.
Signed-off-by: Michael S. Tsirkin
------------------------------------------------------------------------
r549 | mstsirkin | 2015-10-21 17:21:16 +0300 (Wed, 21 Oct 2015) | 6 lines
cl: document resolution for VIRTIO-144
virtio-blk: restore VIRTIO_BLK_F_FLUSH and VIRTIO_BLK_F_CONFIG_WCE
Signed-off-by: Michael S. Tsirkin
------------------------------------------------------------------------
r550 | mstsirkin | 2015-10-21 17:21:41 +0300 (Wed, 21 Oct 2015) | 6 lines
cl: document resolution for VIRTIO-145.
pci: clarify configuration access capability rules
Signed-off-by: Michael S. Tsirkin
------------------------------------------------------------------------
r551 | mstsirkin | 2015-10-21 17:22:09 +0300 (Wed, 21 Oct 2015) | 6 lines
cl: document resolution for VIRTIO-146.
add advice on transition from earlier drafts.
Signed-off-by: Michael S. Tsirkin
------------------------------------------------------------------------
The TC agrees to include the above change(s) in virtio-v1.0-cs05 and future versions of the specification.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|