OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [office] Tying issues to committee drafts

I'm confused.  I thought cd02 (aka cd01 rev06) is what we are currently
reviewing and we will likely see cd02 rev01, cd02 rev02, etc., until we
decide to declare one of them cd03.  That was the pattern in moving from
initial cd01 to declaration of cd02.

I assume that you apply a resolved issue (in JIRA parlance) when you have
actually made the changes to the draft (revision) you are working on.
Although technically, it would not be fully applied until it survived into
an approved cd?

(This reminds me of checking code into a build.  The code is not deployed,
however, until a release is cut.  There is usually some regression progress
to determine that a change survived properly into the release.   The release
notes would reflect all fixes since the previous release regardless of the
build in which they were first checked into.  I'm not sure how the analogy
works for us, although it seems that quality assurance of our specification
development has parallels, with the complication of movement from cd
sequence to a cs sequence to an os progression.) 

It seems that it is either possible 

  (1) that the resolution of an issue is applied more than once (progressing
through drafts that preserve it) or 
  (2) we understand that a cd includes all changes applied to intermediate
drafts since the previous cd (including any reversions/replacements of

It might come down to how filtering works best?

 - Dennis

-----Original Message-----
From: Patrick Durusau [mailto:patrick@durusau.net] 
Sent: Tuesday, June 02, 2009 06:52
To: ODF office
Subject: [office] Tying issues to committee drafts


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:


I think that would tie the issues to particular releases with the 
minimum amount of effort.


Hope everyone is having a great week!


Patrick Durusau
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)

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:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]