|
Should the TC accept changes in the description as non material, and Request a
Special Majority Vote for the advancement of the draft virtio-1.1-wd02 as a
Committee Specification virtio-1.1-cs01?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to request a Special Majority Vote to advance the latest working
draft virtio-v1.1-wd02 which matches virtio-v1.1-csprd01 with non-material
changes as a Committee Specification virtio-v1.1-cs01.
Note: this is *not* a vote on releasing the Committee Specification:
if this motion passes, a vote will be initiated by OASIS.
The working draft can be found at:
https://github.com/oasis-tcs/virtio-docs/blob/master/virtio-v1.1-wd02.zip
The above archive also includes:
virtio-v1.1-wd02-diff-from-v1.1-csprd01 - highlighting changes from v1.1-csprd01
virtio-v1.1-wd02-diff-from-v1.0-cs04 - highlighting changes from v1.0-cs04
The TC agrees that the following changes since
virtio-v1.1-wd02-diff-from-v1.1-csprd01 are all non-material changes:
REVISION: update to wd02
acknowledgements: add members and non-members
scripts: ability to diff with multiple versions
gitattributes: make git diff easier to read
editorial: changelog: tweak formatting
editorial: gitlog.pl: generate the changelog
editorial: add changelog since csprd01
editorial: add labels
block: drop duplicate text
conformance: fix confusion about legacy interface
editorial: upgrade links to https
introduction: update link to IEEE 802
conformance: tweak to match OASIS requirements
editorial: explain each structure before use
signal start and end of structures consistently
conformance: add links to crypto and input devices
format: replace "- i.e." with ", i.e.,"
(origin/master) close issue 32
virtio-blk: clarify semantics of multi-segment discard/write zeroes commands
virtio-blk: avoid inconsistent "DISCARD" term
virtio-blk: describe write zeroes unmap semantics
virtio-blk: move virtio_blk_discard_write_zeroes definition
virtio-blk: document data[] size constraints
introduction: simplify the designation of legacy
ccw: be more precise about the semantic of revision 1
note: above changes are all either formatting changes or have
been previously approved by a TC ballot.
The changes are also listed in the revision history chapter of the specification
and highlighted in virtio-v1.1-wd02-diff-from-v1.1-csprd01
and virtio-v1.1-wd02-diff-from-v1.0-cs04.
--------------------------------------
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.
--------------------------------------
|
