Re: Bug tracking systems as information repositories

Subject: Re: Bug tracking systems as information repositories
From: Kimber Miller <kimber_miller -at- acs-inc -dot- com>
To: techwr-l
Date: Tue, 18 Jul 2000 13:14:35 -0500


I can see the benefit to using this kind of system, especially
interesting is the "perception" factor.

My questions:
How do you decide what constitutes a documentation "bug"?
How do you decide who enters these bugs?
Is bug identification limited to whomever is doing the documetation QA,
or anyone doing a literary or technical review?

Thank you,

--Kimber Miller
ACS, Inc.
Dallas, TX USA

"Fagerlund, Kippi" wrote:

> The pubs group I manage uses both bug tracking
> and source control programs, along with the rest of
> Engineering. These tools include VSS and StarTeam, and
> ClearQuest and ClearCase.
>
> One reason I like using bug tracking for documentation
> is that it reinforces the perception that we are part
> of Engineering, and therefore use the same tools (and
> presumably are held to some of the same standards) as
> development and QA. It's also a way to keep things
> from falling through the cracks.







Previous by Author: Re: naming conventions for images
Next by Author: Experience with GUIDS lifecycle methodology?
Previous by Thread: RE: Bug tracking systems as information repositories
Next by Thread: Re: Bug tracking systems as information repositories


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

Sponsored Ads


Sponsored Ads