Software Bug Databases

[jlshaeffer at aol.com]

 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. 

Jim Shaeffer


 







 


________________________________________________________________________
More new features than ever.  Check out the new AOL Mail ! - http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/text.htm?ncid=aolcmp00050000000003