Strategies for dealing with versions?
Oxygen general issues.
-
- Posts: 132
- Joined: Thu Apr 17, 2014 1:55 am
Strategies for dealing with versions?
Post by tomjohnson1492 »
I'm authoring DITA content that has a lot of versions. There are probably 20 different versions of the product. We also want to use a source control like SVN to manage the content and all the versions. Are there specific strategies I should use when versioning content?
For example, should I just store all content for version 2.0 into a file folder with 2.0 in the title? And all content for version 3.0 into a folder with 3.0 in the title? I feel like there's a lot more strategy I should be following when handling versions with DITA content. Any tips?
For example, should I just store all content for version 2.0 into a file folder with 2.0 in the title? And all content for version 3.0 into a folder with 3.0 in the title? I feel like there's a lot more strategy I should be following when handling versions with DITA content. Any tips?
Re: Strategies for dealing with versions?
Hi,
I can't really comment for DITA in specific, but the general rule for development with version control systems (I'm thinking of SVN here) is that you work with a trunk, branches and tags.
You can read around the web a bit about what these three concepts ('trunk', 'branch' and 'tag') refer to:
http://stackoverflow.com/questions/1614 ... positories
Do you actively develop all these versions in parallel?
Are they versions of the documentation or do they each represent the documentation for a different version of a product. Do the versions have an ancestry with a previous/older version?
Regards,
Adrian
I can't really comment for DITA in specific, but the general rule for development with version control systems (I'm thinking of SVN here) is that you work with a trunk, branches and tags.
You can read around the web a bit about what these three concepts ('trunk', 'branch' and 'tag') refer to:
http://stackoverflow.com/questions/1614 ... positories
Do you actively develop all these versions in parallel?
Are they versions of the documentation or do they each represent the documentation for a different version of a product. Do the versions have an ancestry with a previous/older version?
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 132
- Joined: Thu Apr 17, 2014 1:55 am
Re: Strategies for dealing with versions?
Post by tomjohnson1492 »
Thanks for the info. Different customers use different versions of the product, so we have to maintain valid doc for each version. Your response answers my question. I am aware of how software teams use version control, and I guess we might follow the same pattern. Thanks,
Tom
Tom
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service