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.
Subject:Document revision control From:Kate Kane <KGKANE -at- ACCUSORT -dot- COM> Date:Wed, 26 Nov 1997 15:52:17 EST5EDT
We're trying to come up with a method for controlling hardware and
software document revisions. The main issue is what constitutes
enough of a change to warrant a revision number increase, for
instance going from 1.0 to 2.0 as opposed to going from 1.0 to 1.1
(I'm talking about technical changes here, not grammar, typos, etc.)
Our products are constantly being changed, so we have to make sure
users are getting the correct document. Information about archiving
methods would be appreciated, too.
Can anyone suggest any resources for learning about this? The only
thing I have been able to find on the internet is about software
packages, but nothing about theory (why, when).
Thanks for your help.
kgkane -at- accusort -dot- com