RE: "Bug" reporting for documentation?

Subject: RE: "Bug" reporting for documentation?
From: "Humbird, LenX" <lenx -dot- humbird -at- intel -dot- com>
To: "'Dawson McKnight'" <dawson_mcknight -at- hotmail -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 13 Jul 2000 14:27:51 -0700

We're doing that here at Intel, except we're using Visual Source Safe (VSS)
instead. This ensures that documentation is held to the same control and
quality standard as code. It's also for accountability as well. People know
what got changed and by whom. So when it comes time to blame and
finger-point, VSS is the smoking gun of choice.

> -----Original Message-----
> From: Dawson McKnight [mailto:dawson_mcknight -at- hotmail -dot- com]
> Subject: "Bug" reporting for documentation?
> Should source code management tools be used to report "bugs" in
> documentation?
> My company recently started using StarTeam for documentation version
> control. The software works well enough for that purpose,
> but it is being
> suggested, much to my chagrin, that we should use StarTeam
> (which in its
> full-blown form is really meant to manage code) to report all
> major "bugs"
> in our documentation (excluding grammar and spelling mistakes -- but
> substantive changes can be numerous and extensive).
> Am I crazy, or is this the bad idea that it smells like to
> me?

Previous by Author: RE: Skills
Next by Author: RE: What's another name for QA?
Previous by Thread: Re: "Bug" reporting for documentation?
Next by Thread: RE: "Bug" reporting for documentation?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads