Re: Calling a Bug a Bug

Subject: Re: Calling a Bug a Bug
From: Pat Anderson <panders -at- aw -dot- sgi -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 10 Mar 2003 15:33:44 -0500


At 03:05 PM 3/10/2003 , tgr -at- lanminds -dot- com wrote:
>
>Comrades,
>
>What term do you use when referring to bugs in release notes? Do you call
>them bugs or are they something else? I have heard them referred to as
>imperfections, for example. Any opinions?
>
>- t
>

"Limitations and Solutions" instead of "Bugs and Workarounds".

...pat.
Pat Anderson
StudioTools Documentation Manager
Alias|Wavefront, a Silicon Graphics company
panders -at- aw -dot- sgi -dot- com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Order RoboHelp Office X3 by March 14 and receive a $100 mail-in rebate,
plus FREE WebHelp Merge Module and FREE iMarkup Software, for a
total giveaway value of $439! Order today at http://www.ehelp.com/techwr-l

Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



References:
Calling a Bug a Bug: From: tgr

Previous by Author: Has anyone used tool for extracting comments from code?
Next by Author: Re: Usability ROI
Previous by Thread: Calling a Bug a Bug
Next by Thread: Re: Calling a Bug a Bug


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


Sponsored Ads