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.
Beth Scudder's Friend asks> Is there such a thing as an electronic revision
database system for
> technical writing? The programmers here have a bug database in which they
> register all the bugs and then fix them whenever they get the time. We
want
> our own database so that when someone says, "this thing should go in the
> manual," we can enter it as a change to make for the next revision.
>
We use Track (Bug Track Software) for both the development bugs and the
documentation bugs/change requests. I search for my bugs and keep them up to
date, just like rest of the R&D team. I recommend you try to be included in
whatever your developers are using, it never hurts to be part of the larger
team.
