[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Correction: was Re: [office] Tying issues to committee drafts
Greetings! Sorry for the confusion but OpenDocument-v1.2-committeeDraft-01 appears under 1.2 drafts as a committee draft while the *correct* latest version appears under specifications as: OpenDocument v1.2 part 1 Committee Draft 2. So, the next committee draft version would be: OpenDocument v1.2 part 1 Committee Draft 3. Sorry 'bout that. Hope everyone is having a great day! Patrick Patrick Durusau wrote: > Greetings! > > I would like to suggest that a *placeholder* be created for the next > committee draft version be created in JIRA so that as I "apply" > resolutions, I can assign those issues to that particular committee > draft. > > Note that such a draft does not *yet* exist but that will tie a > particular set of issues to a given draft, such that when that draft > is approved by the committee, it is possible to know what issues were > addressed by that draft. > > It is certainly the case that if in the approval process an issue > needed further discussion or revision, its assignment could be changed > so that it isn't tied to that committee draft. > > We are now at: OpenDocument-v1.2-committeeDraft-01 so I would suggest > the placeholder for the next version would be: > > OpenDocument-v1.2-committeeDraft-02. > > I think that would tie the issues to particular releases with the > minimum amount of effort. > > Comments/suggestions? > > Hope everyone is having a great week! > > Patrick > -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]