[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-359) Delete old guides from git

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792567#comment-12792567 ] 

Michelle Murray commented on TOOLSDOC-359:
------------------------------------------

In summary/update, at this time there are 3 Jenkins jobs:
* jbosstools-docs_40 = JBT 4.0.x docs, currently at version 4.0.1
* jbosstools-docs_41 = JBT 4.1.x docs, currently at version 4.1.0
* jbosstools-docs-nightly = JBT docs in master branch so under development, aiming at 4.2.x or 5.0.x (whatever is deemed to be the next JBT version)
                
> Delete old guides from git
> --------------------------
>
>                 Key: TOOLSDOC-359
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-359
>             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.0
>            Reporter: Michelle Murray
>            Assignee: Michelle Murray
>
> 4.1.x onwards docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/docs
> 4.0.x & prior docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/guides
> The older guides are also located in 4.0.x branch.
> 1. I propose deleting the guides dir in master branch to avoid future confusion about which docs are current.
> 2. Removing the guides dir from master will break https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs-nightly/.
> * In short term can probably solve this easily by redirecting the jenkins job to the 4.0x branch.
> * In long term, need to revise jenkins job to only build the JBT user guide https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/JBoss_Tools_User_Guide.

--
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