Hi Michael,
I saw your note & thought you might be interested to know that the OpenC2 TC is taking this approach. They are currently at CSD04 (see http://docs.oasis-open.org/openc2/oc2ls/v1.0/ ) and they added an editor's note to the start of their spec explaining how they are following an agile development approach. You are correct that the approvals must be official. It is by Full Majority Vote and you can do that in a meeting if you have a quorum. (In their editor's note, they fail to mention the public review before CS approval but the editor tells me that they expect to do that after their next CSD.)
/chet
On Tue, Jun 19, 2018 at 11:27 PM, Michael S. Tsirkin <
> wrote: Hello! I think we should try to start doing time-based releases. Drafts: - Ideally we'd just do periodic snapshots say once each two weeks. Unfortunately it seems that OASIS requires us to vote on releasing every draft. Should be a quick vote though.
Public Release Drafts:
- Let's try to do say twice a year?
Things we'll probably see in the next one: - packed rings - SRIOV
Things we might see: - crypto - vsock - input - gpu
too much to hope for: - 9pfs - procrpmsg
--
MST
------------------------------
------------------------------
---------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/ apps/org/workgroup/portal/my_ workgroups.php
--
/chet
----------------
Looking forward to Borderless Cyber 2018 ,
3-5 Oct
, Washington, D.C.
Organized by The World Bank, OASIS, and Georgetown University
Chet Ensign Chief Technical Community Steward OASIS: Advancing open standards for the information society http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
