Bug 806728

Summary: RFE: Easy Branching of All Topics for a Project
Product: [Community] PressGang CCMS Reporter: Tim Hildred <thildred>
Component: Web-UIAssignee: pressgang-ccms-dev
Status: NEW --- QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 1.xCC: topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tim Hildred 2012-03-26 05:27:50 UTC 
Description of problem:
Part of our current work flow involves branching our documentation in SVN for a release, to provide stable files for translation to work on while development continues in the newer branch. 

For example, in preperation for the 3.0 RHEV release, we committed our XML changes to a /3.0/ folder up until the docs freeze. That 3.0 folder was what we handed over to translation. All further development work took place in a 3.1 directory. 

This different from a snapshot, because we are able to update the 3.0 folder when we get high priority bugs that apply to both the 3.1 and 3.0 documentation. When this happens, we back port our change, and update a translation ticket. 

We would like to see the ability to clone topics forward for a release. So that when we GA 3.1, we can clone all the topics forward to 3.2, and continue development of information and leave stable topics for translation.
Comment 1 Eric Johnson 2012-10-23 15:37:47 UTC 
It would be good to also include the ability to label snapshots of a topic set as well so that re-useable topics can be more easily identified.

The branching mechanism should manage revision history such that the history for all versions of a topic, on all branches, can be visualized.