TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Future use From:Kimberly Green <kimberly -dot- green -at- CHEETAHNET -dot- COM> Date:Tue, 24 Feb 1998 08:53:50 -0500
We use "Not available in Version 1.1" (the version number for the
release we are documenting). This is not a positive selling phrase, it
just states the fact and does not promise anything.
I am in a very similar situation. I am trying to document a constantly
changing software product with changing priorities and changing
schedules. Does anyone have any tips for working effectively in this
From: Marci Abels[SMTP:mabels -at- CSIKS -dot- COM]
Sent: Tuesday, February 24, 1998 8:34 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Future use
I know this has been discussed before, and I've looked in the
and am still looking for a better way. We are documenting a
software package. Several features are not yet operational,
are planned for future implementation, some features are on the
not operational because they are now obsolete, as far as the
are concerned, and some features are still up in the air
In the past, I used "For future release" which served us well.
iteration, however, we have several features that will go away,
them were operational in the past but are no longer so. Some
planned for future implementation, but have been dropped from
planning schedule for various reasons. And sill others will
be implemented, as soon as the programmers have time. I tried
"Implementation currently under review" but we have some people
dislike that. So, I am looking for a statement to use that holds
promises for the future, but says "Don't bother with this, it
work now." Of course, we wnat something more positive than the
truth, that the feature is not operational and we don't really
it ever will be. :-)