RE: Address this. . .

Subject: RE: Address this. . .
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: "kathleen -at- writefortheuser -dot- com" <kathleen -at- writefortheuser -dot- com>
Date: Fri, 12 Mar 2010 13:48:26 -0500

So, you've never looked at something that somebody thought was a good idea and decided:

a) that it wasn't really such a good idea


b) that there's nothing wrong with the idea, but we don't have time or resources


c) its a good idea, but we're getting some new infrastructure next year, so there's no
point expending the effort to patch the current process when it's all going to change anyway...

You wouldn't consider performing the research, discussion and evaluation on any of
those three to be "addressing" them?

- K

From: kathleen -at- writefortheuser -dot- com [mailto:kathleen -at- writefortheuser -dot- com]
Sent: Friday, March 12, 2010 10:14 AM
To: McLauchlan, Kevin
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Address this. . .


Your use could be the standard language that is used in Release Notes, but on first glance, I'd read "To be addressed..." as "will be fixed."

I doubt I'd think twice about it either, which why I, and probably many other people, are annoyed when such bugs aren't fixed.

E.G., everyone's on-going complaint about some of the "features" in MS Word, etc.

LOL, now I know why!

To avoid misinterpretation, you might use a term such as "considered," although I imagine company's prefer a more ambiguous term.


> -------- Original Message --------
> Subject: Address this. . .
> From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
> Date: Fri, March 12, 2010 8:55 am
> To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
> All,
> I'm getting push-back on some standard language in our Release Notes.
> In the list of issues/bugs that are not being fixed for the current
> release, we say "To be addressed in a future release".
> We carefully don't even say "next" release.
> But the problem is the word "addressed".
> Some customer has decided that "To be addressed in a future release"
> means " explicit prmise that the issue is to be fixed exactly how I want it".


The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.


Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


RE: Address this. . .: From: kathleen

Previous by Author: RE: Address this. . .
Next by Author: RE: After all, it is Friday...
Previous by Thread: RE: Address this. . .
Next by Thread: Re: Address this. . .

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

Sponsored Ads