RE: future functionality

Subject: RE: future functionality
From: "Brierley, Sean" <Sean -at- Quodata -dot- Com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 5 Jul 2001 09:38:00 -0400

Personally, I agree.

However, I have fought and lost that same battle here, before. I have even
used, as ammo, older versions of the UG that promised future functionality
that was *never* actually implemented.

All I could do was to present my reasons for not wanting to include such
references in post-sales documents, and my point of view was considered
before I was overruled by folks up the food chain (which is fine, the docs
are company docs, they are *not* mine, personally, so I was and am happy to
have had my say, even if I was overruled).

Cheers,

Sean
sean -at- quodata -dot- com

> -----Original Message-----
> From: Field, Kristin [SMTP:KField -at- LSAC -dot- org]
>
> I am currently updating a user's manual from a year and a half ago written
> by a different author. There are several references in the manual of
> future
> funcionality for the particular application I am updating the manual for.
> For example, "The XXX allows you to do YYY. In a future release, you
> will
> be able to do ZZZ." Personally, I think this is a bad practice and don't
> feel that any future plans for the application should be in a user's
> (basically a "How to") manual. I mean, this manual is a year and a half
> old, as I mentioned, and the future functionality is still future
> functionality.
>
> Wouldn't that be best left to the marketing literature?

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

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com


---
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: Pronouns with User
Next by Author: re: future functionality
Previous by Thread: future functionality
Next by Thread: RE: future functionality


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


Sponsored Ads