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] [OASIS Issue Tracker] Commented: (OFFICE-2082) [Zip] referenceis neither public nor authoritative


This might have been before you joined the TC (it certainly was before we 
started using JIRA) but I did a complete review of our references and 
posted my recommendations here:

http://markmail.org/message/s7orbvfya2ztq7wv

And details uploaded here:

http://www.oasis-open.org/committees/document.php?document_id=31301


-Rob

"Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 10/11/2009 
07:21:25 PM:


> Subject:
> 
> RE: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) [Zip] 
> reference is neither public nor authoritative
> 
> Rob,
> 
> I only did this because I had this one in my job jar to deal with 
> for Part 3 already and I just hadn't put up the JIRA issue yet. 
> This topic has come up in discussions, just didn't make it into a 
> JIRA issue.  It was at the top of my list of pending Part 3 items.
> 
> I'll watch for any duplicates that arise out of the automated 
> procedure. No worries.
> 
>  - Dennis
> 
> -----Original Message-----
> From: OASIS Issues Tracker [mailto:workgroup_mailer@lists.oasis-open.org
] 
> Sent: Sunday, October 11, 2009 14:28
> To: office@lists.oasis-open.org
> Subject: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) 
> [Zip] reference is neither public nor authoritative
> 
> 
>     [ http://tools.oasis-open.org/issues/browse/OFFICE-2082?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=16257#action_16257 ] 
> 
> Robert Weir  commented on OFFICE-2082:
> --------------------------------------
> 
> Dennis, in the future please don't open new JIRA issues 
> corresponding to public comments.  I have automation that will 
> automatically do this for all public comments, and I have no easy 
> ability to tell which public comments have had JIRA issues opened by
> TC members and which ones have not.  So when we both do the 
> transfer,  we will end up with duplicate issues in JIRA pointing to 
> the same public comment.   It also may give the wrong message to the
> other people who submit public comments and do not see an immediate 
> personal message saying that we've opened a JIRA issue for them. 
> Better to Just wait for the batch transfer of comments to occur like
> we've done for the other 1500 or so public comments.  Nothing gets 
> lost that way. and nothing gets duplicated.   Thanks!
> 
> [ ... ]
> 



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