Re: Version vs. Revision

Subject: Re: Version vs. Revision
From: "Wittel, Teresa J." <WITTTJ -at- NCSLINK -dot- COM>
Date: Wed, 13 Aug 1997 10:42:00 -0700

Suzanne Lee suggested (below) that using version could be confusing to
the users if the software didn't match the documentation. I can see her
point. Our documentation has a version number, followed by a release
number and a fix number. (Ex: 3.01.03) It always matches the code
version numbers. How can you keep track of which documentation supports
which code without matching the version numbers?

BTW, I have no aversion to using the revision system and even have used
a combination of version and revision to describe a release. (Ex:
Version 3.0, Rev. A) It all depends on what my employer has developed to
track the products.

>Kevin asked:

>> what was used more: Revision or Version.
>>
>> For Example:
>>
>> Document A, Rev. A, B, C, etc.
>> Document A, Version 1, 1.1, 1.2, 2.0, etc.

>I have no idea which is more common, but we used to use version for our
>manuals, until we found out that it caused users got confused because it
>didn't match the software version (software version 8.0, document version
>6.0).

TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html


Previous by Author: More he, she and whomsoever
Next by Author: Re: being anal
Previous by Thread: Re: Language rules
Next by Thread: Online Help references


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

Sponsored Ads


Sponsored Ads