Consistent version numbering across drafts & deliverable Laurent VRECK, ETSI Standardization Projects laurent.vreck@etsi.org

Reasons (1) "TTCN-3 Part 6 ", or "TCI "  Most ETSI deliverables are being revised several times  Delegates often don’t refer to a document by its WI number but either by its ETSI number, or just by elements of its title. Element of Title "TTCN-3 Part 6 ", or  "TCI " ETSI Nb ES 201 873-6 WI Nb DES/MTS-00063-6[2] (published as v1.1.1) RES/MTS-00090-6 (published as v3.1.1) RES/MTS-00090-6[2] (published as v3.2.1) RES/MTS-00090-6[3] ( draft to be published as v3.3.1) RES/MTS-00107-6 (new WI for edition 4.1.1)  hence the need for a coherent version numbering across multiple revisions of deliverables and their drafts.

Reasons (2) THIS: Never again… ;-) 0097-3v251_FinalVersionCleaned_LaurentCommentsAdded_RevisedNSNOK_ ReadyFor2ndApproval.doc Never again… ;-)

Keeping consistent versioning across drafts & deliverable Version nb Goal: Agree on clear and simple common practice Improve & unify Drafts & Deliverables version numbers Ultimate goal: Provide easy and quick access to reliable and accurate project data. make information retrieval easier

Basic Rules Each time a document(*) is modified its version is incremented (even if only a comma is changed in the text) v0.0.4 + ";" = v0.0.5 Version numbers NEVER go backwards The version number identifies the current version of the present document(*), it does NOT identify a foreseen future publication version. (*): document = draft OR deliverable Draft : a working document, not yet published Deliverable: a published ETSI document Terminology

Draft & deliverable versioning Use of the 3-digits version number Vm.t.e m incremented for a major new version t incremented for new version with technical changes e incremented for new version with editorial changes Draft : a working document, not yet published Deliverable: a published ETSI document Terminology

Consistent versioning … Avoid exotic practices Exotic practice : Increment digits without reseting least significant ones. to be avoided ? Prefered practice : reset least significant digit(s) when incrementing more significant digit. v0.0.2 v0.0.2 v0.1.2 v0.0.3 v0.1.3 v0.1.0 . v0.1.1 v0.1.14 v0.1.2 v0.2.14 v0.2.0 v0.2.15 . . v0.7.4 v0.7.21 v1.0.0 v1.7.21 PUB PUB Draft : a working document, not yet published Deliverable: a published ETSI document Terminology

Consistent versioning … Version numbers NEVER go backwards YES NO v0.3.0 v0.3.0 v0.3.0 New WI v0.3.1 v0.3.1 v0.3.2 v0.3.2 v0.4.0 v0.4.0 v0.4.1 ES 201 873-6 v1.1.1 PUB PUB v0.4.1 v1.1.1 v1.1.2 v0.4.2 New WI v1.2.0 v0.5.0 v1.3.0 v0.6.0 . . . ES 201 873-6 v2.1.1 PUB PUB Draft and deliverable versions belong to the same sequence Draft : a working document, not yet published Deliverable: a published ETSI document Terminology

Consistent versioning … Accross editions DRAFT PUBLICATION First edition v0.2.0 New WI v0.3.0 v0.3.1 v0.3.2 v0.4.0 v0.4.1 (D) TS 183 004 v1.1.1 PUB Second edition New WI v1.1.2 New major version v1.2.0 v1.3.0 (R) TS 183 004 v2.1.1 . PUB Third edition v2.1.2 Not a new major version, but technical changes New WI v2.2.0 v2.3.0 (R) TS 183 004 v2.3.0 PUB

History Box Information filled in by the rapporteur at the last page of a draft document : Document history <Version> <Date> <Milestone> 0.0.4 22 October 2007 Include feedback from Yongwei Wu on CGSP of ChinaGrid 0.0.5 23 October 2007 Merge my changes with those from Laurent on CGSP 0.0.6 24 October 2007 Merge diffs from Clement Mathieu 0.0.7 25 October 2007 OAR screenshots, BNF grammar for host lists 0.0.8 26 Oct. 07 Added def for ARCFileTransfer subtype, updated schema in annex C 0.0.9 26 October 2007 Fixed mistake in ARC file transfer type def 0.0.10 7 November 2007 Reordered ‘directory’ child node in Load Leveler def OR 0.0.11 November 2007 CR001, 002, 003, 005 implemented after meeting 0.0.12 December 2007 Spell check, see rev-marks 0.1.0 January 2008 CR006 (Ericsson) implemented 0.2.0 March 2008 CR007, 008, 009, 010 implemented 0.2.1 April 2008 Title changed as described in agreed CR011. READY for APPROVAL

Revision Marks Useful word processor feature allowing to keep track of changes made by one or more users over time.

‘Reviewing’ toolbar Turning ‘rev-marks’ ON

Drafts Location Between meetings Before meetings Drafts must be uploaded in the «70-Draft » area of the server Discussions take place on the TB mailing list Before meetings Last version should be made available as a meeting document. If it is for approval during the meeting it MUST be made available as a meeting document. Contributions against drafts are submitted as meeting documents and discussed during the meeting

Questions?