RE: Calling a Bug a Bug

Subject: RE: Calling a Bug a Bug
From: Matthew Horn <mhorn -at- macromedia -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 10 Mar 2003 15:13:11 -0500


When it's been fixed, we call it a Bug. When it's not fixed, we call it a Known Issue.

Matthew J. Horn
Sr. Technical Writer
< m a c r o m e d i a >

> -----Original Message-----
> From: tgr -at- lanminds -dot- com [mailto:tgr -at- lanminds -dot- com]
> Sent: Monday, March 10, 2003 3:05 PM
> To: TECHWR-L
> Subject: Calling a Bug a Bug
>
>
>
> 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?
>

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

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.



Previous by Author: RE: Has anyone used tool for extracting comments from code?
Next by Author: RE: Calling a Bug a Bug
Previous by Thread: RE: 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