[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] (OASIS Issue Tracker) Commented: (OFFICE-1700) EditorNote: Section 18.258 style:font-charset
Dennis, You know, I don't just make this stuff up to irritate you. ;-) From Micheal's post of 29 May 2009: > My proposal how we proceed is: > > Whoever has time and and interest may comment on an item, and may > provide a resolution. This resolution is recorded in the "proposal" > field. If a proposal for a resolution does exist, the proposer of the > resolution sets the status of the issue to "resolved". > > Patrick (or myself if an issue affects the schema) takes the issues > whose status is "resolved" and applies the proposed resolution to the > specification text. He then sets the status to "Applied". > > The changes to the specification still will be recorded. We continue to > have a week for TC internal reviews of drafts before we vote on them in > a TC meeting, or we conduct electronic ballots for committee drafts, > that run at least a week anyway, so that there is the same time > available for a review. > > TC members therefore have the choice to either watch the items in JIRA, > or to just review the changes in the next draft. The approval of a > resolution takes place with the approval of a committee draft. This > means that nothing that we do in JIRA implies any kind of approval by > the TC, and that it is not required to watch the changes in JIRA to > figure out what changes are made in a draft. > > When a draft has been approved as committee draft, all issues applied to > that draft are closed (unless someone has objected to a particular > resolution). See: http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200905/msg00451.html Closing down for the day. Have to go let my chickens out in the yard for a bit. ;-) Hope you are having a great day! Patrick Dennis E. Hamilton wrote: > Patrick, my understanding of "resolved" in JIRA is that it means resolution has been *agreed*, "applied" in JIRA means, in my understanding, that the resolution has been implemented. > > A brand new JIRA issue could contain a proposed resolution. > > I think we need to reaffirm exactly at what point something becomes resolved. > > (There may be a special case around editorial matters where you get to declare something resolved. In that case, I suppose, someone would need to open a new issue in order to object to your determination.) > > - Dennis > > -----Original Message----- > From: OASIS Issues Tracker [mailto:workgroup_mailer@lists.oasis-open.org] > Sent: Monday, June 15, 2009 14:22 > To: office@lists.oasis-open.org > Subject: [office] [OASIS Issue Tracker] Commented: (OFFICE-1700) Editor Note: Section 18.258 style:font-charset > > > [ http://tools.oasis-open.org/issues/browse/OFFICE-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11901#action_11901 ] > > Patrick Durusau commented on OFFICE-1700: > ----------------------------------------- > > Sigh, all "resolution" means as used here is that a proposal has been made. Even if I "apply" the proposal, the issue has not yet be "closed." > > We have to somehow move the issues through JIRA. I look for "resolved" issue to consider the proposals and make further comments if it seems unclear to me or to need further discussion. > > Granted the process semantics aren't what I would choose starting from a blank slate, but that wasn't an option. > > [ ... ] > > > -- 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]