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.
If so, what I've done in the past is that each time a version is
published, I do a revision comparison and print the document as well as
save it as that version.
OTOH, with unlimited money and resources, you could implement a system
such as Documentum. I used it at a previous gig amd everytime I'd check
out a new document, wortk in it, save it, and check it back in, it
automaticaly saves the version as well as all previous versions (some of
my web pages were updated by an external system multiple times a day and
had hundreds of previous versions).
> My question: As we bring a state online, we develop a standard ?set?
> of documentation for each state. But, as we move forward and the
> product/state changes, the documentation needs to change, also. What
> is the tried and true method of tracking changes (versions) to
> documentation? The company wants to track where the state ?was? and
> were it currently is. I am looking into implementing PVCS Version
> Tracker, but I?m not sure if this is the best method. Any
> suggestions/advice?
=====
John Posada
jposada01 -at- yahoo -dot- com
john -at- tdandw -dot- com
732-291-7811
A duck's quack doesn't echo, and no one knows why.
__________________________________________________
Do You Yahoo!?
Send instant messages with Yahoo! Messenger. http://im.yahoo.com/
