doc release numbering

[Beth Agnew]

If you have versions of product and versions of documentation, I think 
that can get very confusing for users. "Do we use version 2.1 of the 
manual with product 3.1 or is it the other way around?" I like the 
version of the documentation to exactly match the version of the 
product. Whether it's hardware, software, or some other product, 
whatever we call it should let the customer know which product feature 
set they are using, and the documentation should clearly indicate that 
these documents cover that specific feature set.

In the world outside techcomm, publications are often issued as second, 
third, fourth editions. One expects the content to be updated with 
subsequent editions. Readers also know to open the cover and look at the 
copyright page for additional date and "version" (edition) information 
if they can't get that info from the cover.

Evans, Diane L (Rosetta) wrote:
> I would call it "Version B."  Other choices are "Verion 1.1" or "Version
> 1.0.1." 
-- 
Beth Agnew
Presenting "Podcasting & Vidcasting: The Future of TechComm"
at the STC Conference, Las Vegas, NV, 2 p.m. May 10, 2006

Professor, Technical Communication
Seneca College of Applied Arts & Technology
Toronto, ON 416.491.5050 x3133
http://www.tinyurl.com/83u5u
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: file:///C|/DOCUME%7E1/BETHAG%7E1/LOCALS%7E1/TEMP/nsmail-1.txt
Url: http://lists.techwr-l.com/pipermail/techwr-l/attachments/20060503/9b932f1a/attachment.txt