dita-techcomm — archive

Groups - Release Management Stage 2 proposal DRAFT uploaded

From: Tom Cihak <[email protected]>
To: [email protected]
Date: Mon, 06 May 2013 05:34:00 -0000

The release management proposal has been updated. Please try to review it before the next meeting. Here are some notes about the revision: - Some items that appear as lists in the proposal template were recast as tables for review. - I added a very simple medical device industry example. This should be fleshed out if desired. - Some text [[in two square brackets]] is from the template, left as explanation or placeholder Please consider the following issues: - The date/time formats should be discussed. Do we want separate elements for hours, minues, and seconds, or do we want to use a single element for time? (Likewise for the date.) - Will this domain be included in maps? If so, where? - Are there further elements that should be specialized from data? Change type (addition/deletion/edit) and resolution (accepted/rejected) spring to mind. Thank you. with best regards Tom Cihak NMG Information Development Freescale 512.996.5072 From: [email protected] [mailto:[email protected]] On Behalf Of Cihak Thomas-R65612 Sent: Wednesday, May 01, 2013 11:03 AM To: JoAnn Hackos Cc: [email protected] Subject: RE: [dita-techcomm] Groups - Release Management Stage 2 proposal DRAFT uploaded Hi JoAnn, I have a couple of questions for you. First, have we left out any of the basic requirements of your case(s)? Here is what I added to the proposal: - product group responsible for the change -- which product is this - regulatory relevance -- ISO, FDA, a specific IEEE requirement - functional area requesting the change -- engineering, support - localization required -- yes/no - function responsible for validation - identify who made the change (secure ID) - time and date of the change to the second - nature of the change -- draft comment, including if change is valid for each reuse of the content (metadata -change) - resolution of the change: accepted, rejected, and so on - some way of marking the exact location of the change in the content of the topic Next, are there any of these requirements that can’t be accommodated with the current bookchangehistory domain elements? Thanks very much. with best regards Tom Cihak NMG Information Development Freescale 512.996.5072 From: JoAnn Hackos [ mailto:[email protected] ] Sent: Monday, April 29, 2013 6:20 AM To: Cihak Thomas-R65612 Cc: [email protected] Subject: Re: [dita-techcomm] Groups - Release Management Stage 2 proposal DRAFT uploaded Thanks, Tom Could you and or Seth handle the call today? It would be good to review this with all the others. I'm out of town and mostly out of cell phone range this week and next. JoAnn Sent from my iPad JoAnn Hackos Comtech Services Inc 710 Kipling Street Suite 400 Lakewood CO 80215 On Apr 28, 2013, at 11:09 PM, "Cihak Thomas-R65612" < [email protected] > wrote: Hi JoAnn, I have updated the proposal with the very basics of the medical device industry requirements, mostly taken from the wiki summary section. I obviously don’t understand their requirements as well as you do, so please edit it as you see the need. I made almost no other changes, pending a discussion during the call. Thank you. with best regards Tom Cihak NMG Information Development Freescale 512.996.5072 From: JoAnn Hackos [ mailto:[email protected] ] Sent: Sunday, March 31, 2013 6:23 PM To: Cihak Thomas-R65612; [email protected] Subject: Re: [dita-techcomm] Groups - Release Management Stage 2 proposal DRAFT uploaded Hi Tom, Thank you for getting this Stage 2 proposal started. However, I assume that you have not looked at the material in the TechComm SC's wiki about release management, which includes use cases that I authored from the medical device industry. The notes include the requirements for this industry for information in the change-history of the prolog that need to be incorporated into this proposal. See https://wiki.oasis-open.org/dita/ReleaseManagementWiki#preview These comments were misplaced under change control. I just duplicated them in Seth's release management info. They need to be taken into account in your Stage 2 proposal because they are an integral part of our discussion in the committee of the release management requirements. We have a lot more requirements than the ones you've developed at Freescale. Let me know if you need to discuss. I hope to make tomorrow's call at 8 am Pacific time. I'm on vacation this week but will try to attend in the morning. I trust Seth is going to chair. Best, JoAnn JoAnn T. Hackos, PhD President Comtech Services Inc. 710 Kipling Street, Suite 400 Denver, CO 80215 [email protected] 303-232-7586 From: Tom Cihak < [email protected] > Date: Monday, March 25, 2013 11:42 AM To: DITA Tech Comm SC < [email protected] > Subject: [dita-techcomm] Groups - Release Management Stage 2 proposal DRAFT uploaded Submitter's message Better late than never (I hope) is the release management stage 2 proposal DRAFT. (I said it was the stage 3 proposal, but I was confused about the state.) A few notes: --Some parts are blank (I marked these with [[ and ]].) --Use cases: if you know of others, we should add them. --Some items in part 1 are blank for now. --I recast the questions in 'Technical requirements' and 'Costs' to tables for ese of use and commenting. Thank you. -- Tom Cihak Document Name : Release Management Stage 2 proposal DRAFT Description DITA 1.3 Stage 2 proposal for feature 13102 (Release Management) Download Latest Revision Public Download Link Submitter : Tom Cihak Group : DITA Technical Communication SC Folder : Standards Date submitted : 2013-03-25 11:42:00