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:Re: Tracking bugs From:"Kristine J. Olberg" <kjolberg -at- IX -dot- NETCOM -dot- COM> Date:Sat, 5 Apr 1997 12:39:36 -0600
----------
> From: geoff-h -at- MTL -dot- FERIC -dot- CA
> I'm helping our developers during the beta testing of our
> first software release. The documentation process is in
> pretty good shape for an _ad hoc_ effort, but the beta test
> itself is going to be a bit chaotic. (Who knew? <grin>) I'm
> currently building a contacts database to let me keep track
I have worked with more than one package that tracks not only bugs but new
projects. IMHO, this is the only way to go if you purchase a package
specifically designed to do just that. One package I'd recommend is PVCS
Tracker, which you can customize to your needs to gather an retain all the
information you specified in your post. I wouldn't create my own method
since these off-the-shelf apps have already done most of the work for you.
Regards...Kris
----------------------------------
kris -at- olberg -dot- com
kolberg -at- actamed -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
