1 / 9

Proposed TOSCA TC Timeline

Proposed TOSCA TC Timeline. March 1, 2012. TC Deliverables. Standards Track Work Products “…is a Work Product produced and approved by a TC in accordance with the TC Process which may be promoted to Committee Specification or OASIS Standard…” Non-Standards Track Work Products

avon
Download Presentation

Proposed TOSCA TC Timeline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposed TOSCA TC Timeline March 1, 2012

  2. TC Deliverables • Standards Track Work Products • “…is a Work Product produced and approved by a TC in accordance with the TC Process which may be promoted to Committee Specification or OASIS Standard…” • Non-Standards Track Work Products • Informative and explanatory • Not subject to the patent licensing and non-assertion obligations requirements of the OASIS IPR Policy • Examples: use cases, primers, formal presentations

  3. Work Products Tracks in a Nutshell • Committee Spec/Note Draft • Multiple iterations, Full Majority Vote • Committee Spec/Note Public Review Draft • External & OASIS notifications, Full Majority Vote • IPR disclosures, public comments & TC responses • 30/15 days, multiple iterations must track deltas • Committee Spec/Note • Prereq: CS(N)PRD 7 days after PR if comments precipitate changes • Special Majority Vote • Specification Track Only • Candidate OASIS Standard • Three statements of use, content essentially freezes , lots admin details • Special Majority Vote, 60 day public review, comments collected/responded to • Changes to spec by Full Majority Vote only (withdraws from public review) • OASIS Standard • Membership vote (15% yes (greater than 25% negative can also fail vote) • Approved Errata

  4. Review Periods

  5. Estimated TOSCA Timeline 2012 Note: The exact process varies according to comments received, TC responses, etc. This timeline is a general guideline. There are also latencies built into the process that are not detailed. • 1 Mar – Baseline CSD1 approved • TOSCA-1 and TOSCA-6 Multiple CSDs approved as WIP documents • 5 July – essentially JIRA issues closed or tabled, CSPRD ballot • 19 July – 1st CSPRD 30 day public review • TC continually analyzes and responds • 18 Aug – 30 day review closes

  6. Estimated TOSCA Timeline 2012 (continued) 1st CSPRD spec changes needed • 23 Aug – TC re-ballots • 30 Aug – 2nd CSPRD 15 day review • 14 Sep - CS ballot (presuming no comments) • 21 Sep – Candidate OASIS Standard ballot, statements of use due • 5 Oct – 60 day review • 29 Nov – Review ends • 13 Dec – Membership vote begins (14 day) • No 1st CSPRD changes needed • 30 Aug - CS ballot (presuming no comments) • 7 Sep – Candidate OASIS Standard ballot, statements of use due • 27 Sep – 60 day review • 22 Nov – Review ends • 29 Nov – Membership vote (14 day)

  7. we plan to create several CSDs. These are in the nature of milestones / works-in-progress. They will not advance to CSDPRD. When we are done with our own internal issues, hopefully in the summer, we plan to advance to our first CSDPRD. Based on feedback Timeline Caveats and Concerns • Timeline based on very aggressive charter timeframe • Variability from • TC Process • Extent and usefulness of public comments • Total “mass” of proposals/issues created • Non-normative deliverables, e.g., primer or use case doc • Driven by proposals? Subcommittee? Other? • Statements of work • Will we have 3 implementations? • Aligned with conformance statements

  8. Timeline Summary • The TOSCA TC plans to create several CSDs. These are in the nature of milestones / works-in-progress. They will not advance to CSDPRD. When we are done with our own internal issues, hopefully around July, we plan to advance to our first CSDPRD. Based on feedback (or not), there might be a second. All things going well, we hope in the fall to create a Candidate OASIS Standard in the fall. • This plan is subject to changes, caveats, and concerns that have been expressed in this presentation.

  9. Aligning JIRA Issues and their WDs with CSDs (milestones) • Each CSD • Comprised of 1 or more Closed JIRA issues that resulted in changes • Each issue that results in changes has a unique WD # • Examples • CSD1 (OASIS and RFC2119 bootstrap doc) • TOSCA-1 (spec WD1) • TOSCA-6 (spec WD2) • CSD2 • TOSCA-4 (spec WD3 based on CSD1) • TOSCA-5 (spec WD4 based on CSD1) • TOSCA-3 (spec WD5 based on CSD1)

More Related