[ https://issues.jboss.org/browse/TOOLSDOC-359?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-359: ------------------------------------------ Thanks [~nickboldt]. I think it is all pretty much as you said. Regards Jenkins jobs, as I see it: * Not sure how often 4.0 will need to be rebuilt. The docs are so flawed that I am just leaving them alone. But having a jenkins job won't do any harm for the eventuality that something does need fixing or someone else is wanting to take on the job of fixing (as in TOOLSDOC-316). * Will need a job for developing docs (from master). As soon as 4.1 is released then this branch will be developing towards 4.2. * Once 4.1 is released and branch 4.1 created, will need a job for this so we can fix bugs in docs and applying changes that I didn't get time for prior to GA. Creating the 4.1.x branch should coincide with GA rather than be done in advance, since as far as I can see docs doesn't need stabilized docs for Betas and leaving until GA negates the need to apply changes to master and 4.1 branch continually. -- 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