[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [office] (OASIS Issue Tracker) Commented: (OFFICE-1700) Editor Note: Section 18.258 style:font-charset
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. [ ... ]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]