TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> I don't see much need to use a version control system with
> FrameMaker files.
> Simply storing all Frame files on a server, and insisting
> everyone work from
> the server, keeps two people from modifying the same file at
> once. This
> setup lets everyone work on different chapters, while
> preventing overlapping
> edits in the same file. It let us get our work done really
> fast at this one
> company where I worked, where project timelines were short.
>
> I'm not clear on why folks are concerned with saving every
> little historic
> modification that was ever made to a book file. It's not like
> this is code.
> It's not crucial to product operation; it's just phrasing.
[deletia]
While in general I would agree with you, in some situations a finer level of
version control and change management is very useful and even necessary. If
you want to single-source your docs and apply them against a cross-section
of applications and functionality (such as when you have a core product with
different customizations for different clients), then a finer level of
granularity than "chapter" is a must.
cheers,
brent
--
Brent Jones, Documentation Manager
Versatile Software, Boulder CO
brent -dot- jones -at- versatilesoftware -dot- com
