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: Software Bug Databases From:jlshaeffer -at- aol -dot- com To:baj357 -at- gmail -dot- com, techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 05 Dec 2007 20:59:24 -0500
In my experience, only the writer can judge the doc impact. Some things that seem minor to developers can be major in the documentation and the reverse is true, as well.
I also found it useful to peruse the reported bugs that did not reference the documentation directly, so that I could get "ahead of the curve" and anticipate documentation impacts that non-writers did not consider. It seems like more work, but it saved a lot of rewrite time.
At least you have access to the bug database and get the documentation bugs written up in it. Some writers aren't even that lucky. Documentation really needs to be part of that system.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-