[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-475) Freeze JBDS 7.1 PressGang content specs

[Michelle Murray (JIRA)]

     [ https://issues.jboss.org/browse/TOOLSDOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Murray updated TOOLSDOC-475:
-------------------------------------

     Original Estimate: 2 hours, 20 minutes
    Remaining Estimate: 2 hours, 20 minutes

    
> Freeze JBDS 7.1 PressGang content specs
> ---------------------------------------
>
>                 Key: TOOLSDOC-475
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-475
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: General documentation issues
>    Affects Versions: 4.1.2
>            Reporter: Michelle Murray
>            Assignee: Michelle Murray
>             Fix For: 4.1.2
>
>   Original Estimate: 2 hours, 20 minutes
>  Remaining Estimate: 2 hours, 20 minutes
>
> 1. Make a 'JBDS 8.0.z' release tag in PressGang following [1] Proc 5.4 and completing fields based on 'JBDS 7.1.z' tag values.
> 2. Make new JBDS 8.0 content spec for each 7.1 doc [3] by:
> i) copying 7.1 spec content into a new content spec
> ** some are frozen and some are not - we'll worry about this later
> ** only 1 RN document needs making so *don't* copy both 7.1.0 and 7.1.1
> ii) deleting the ID line
> iii) changing product version to 8.0 (4.2 for JBoss Tools User Guide)
> iv) jira version is 4.2.0.GA (not set for JBoss Tools User Guide)
> v) adding the 'JBDS 8.0.z' tag
> vi) SAVE
> 3. Freeze each 7.1 content spec on the server following [2] Proc 4.5 - step 3 only; *note* - only 2 docs need freezing, Integration Stack and 7.1.1 RNs.
> [1] http://docbuilder.usersys.redhat.com/13968/#Add_a_New_Tag
> [2] http://docbuilder.usersys.redhat.com/13968/#Freeze_a_Map1
> [3] http://skynet.usersys.redhat.com:8080/pressgang-ccms-ui/#ContentSpecFilteredResultsAndContentSpecView;query;tag665=1;logic=And

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira