You work at a software company, right? Your engineering department is probably already using a version control system such as Subversion, Team Foundation Server, or Perforce, so it would probably be easiest to use that.
The one exception would be if they're using Git, which is not well suited to unstructured FrameMaker's binary source format or the normal FrameMaker workflow where you want to make sure only one person at a time edits a file. If you can't use the same system due to license costs or whatever, I recommend Subversion, since it's free and works as well as any of the commercial products. On Fri, Jul 1, 2016 at 5:26 AM, Tornquist, Patti <[email protected]> wrote: > Good morning Framers -- > > > (Unstructured FrameMaker 2012) > > We are currently versioning our content using a folder structure - we create > a folder with the release level and copy all of the Frame files from the > previous release to the new release, increment the version in the books and > online help, and begin adding content. > > > This is not bad for very active content that is regularly changing. However, > for content that is stable and unchanging, there is a fair amount of overhead. > > > We're considering making some changes, and I wondered what others are doing - > how are you handling versioning of Frame content? _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected]
