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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

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


Subject: Re: [sca-bindings] How to handle update history and JIRA for cd03


I don't see why we can't do (3).
I think we can point to a CD and say that the issue is applied in that 
CD as well as closed because of that CD.

-Anish
--

David Booz wrote:
> (3) is what we do in Policy
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
> 
> Inactive hide details for Simon Holdsworth ---06/26/2009 05:23:39 
> AM---Anish (and anyone else for comments), I'm trying to workSimon 
> Holdsworth ---06/26/2009 05:23:39 AM---Anish (and anyone else for 
> comments), I'm trying to work out the best approach for WS and JMS bindin
> 
> 
> From:	
> Simon Holdsworth <simon_holdsworth@uk.ibm.com>
> 
> To:	
> "OASIS Bindings" <sca-bindings@lists.oasis-open.org>
> 
> Date:	
> 06/26/2009 05:23 AM
> 
> Subject:	
> [sca-bindings] How to handle update history and JIRA for cd03
> 
> ------------------------------------------------------------------------
> 
> 
> 
> 
> Anish (and anyone else for comments),
> 
> I'm trying to work out the best approach for WS and JMS bindings 
> documents in terms of how we handle the update history and links from JIRA.
> 
> I don't think its appropriate to have JIRA point to emails that contain 
> the documents with the issue applications, and we have to insert the 
> applied issues into the document update history somewhere, so I believe 
> we have three possible approaches, would be good to agree on this before 
> uploading cd03:
> 
> 1) Upload the specific documents that were discussed on yesterday's call 
> including the resolved issues in the update history in a new entry for 
> that document, using their existing names, and point JIRA at those 
> documents for those applied issues. Then upload cd03 based on those 
> documents with just name change.
> 2) Upload those documents using the next revision number including the 
> resolved issues in the update history in a new entry for the new 
> revision, and point JIRA at those documents for those applied issues. 
> Then upload cd03 based on those documents with just name change.
> 3) Upload cd03 including the resolved issues in the update history in a 
> new entry for cd03, and point JIRA at cd03 for those applied issues.
> 
> Any preference? 3) is easiest, just don't know if its acceptable to have 
> issues applied in a 'base' CD rather than a revision.
> 
> Regards, Simon
> 
> Simon Holdsworth
> STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
> MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
> Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
> Internet - Simon_Holdsworth@uk.ibm.com
> 
> 
> 
> ------------------------------------------------------------------------
> /
> /
> 
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number 
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU/
> 
> 
> 
> 
> 


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