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:Introduction and Question From:Shannon Kornis <real_mccoy97 -at- yahoo -dot- com> To:TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM Date:Mon, 19 Jun 2000 10:15:17 -0700 (PDT)
Hi, I?m Shannon and I am new to the Tech Writer list. I've worked as a
TW for approx. 5 years and am currently working as a consultant at a
Dot Com company where I document process that don?t currently exist.
Yes, this gig is a real kick in the pants?
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
Shannon M. Kornis
Senior Technical Writer
IntelliTech, Inc. mailto:real_mccoy97 -at- yahoo -dot- com
Do You Yahoo!?
Send instant messages with Yahoo! Messenger. http://im.yahoo.com/