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.
Re: Revision Control - NO! Documentation Management - YES!
Subject:Re: Revision Control - NO! Documentation Management - YES! From:Your Name Here <egail -at- TELEPORT -dot- COM> Date:Wed, 26 Mar 1997 08:36:44 -0800
On Wed, 26 Mar 1997, M. Dannenberg wrote:
> There are a number of documentation management and workflow packages
> designed to meet these kinds of requirements. A revision control package
> for software development is definitely not the way to go. I can imagine
> that in some companies people might say, well we got this nice thingy
> here anyway, so why not use it for documentation. Happened to me, but I
> very quickly came up with 100 good reasons for not doing it, and now
> we're evaluating a couple of real doc management packages.
Would you be so kind as to share the best of those 100 reasons with me
(the list)? I'm facing the same argument now from engineering, and I am
not sure whether the ClearCase version control system will work for our
Thanks in advance.
E. Gail Miedema
Senior Technical Writer
egail -at- teleport -dot- com