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.
RE: Naming conventions for superseded version numbers
Subject:RE: Naming conventions for superseded version numbers From:John Posada <JPosada -at- book -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 8 Oct 2003 11:26:10 -0400
Are there any "standards" which I need to adhere to for numbering superseded
manuals/Help files; e.g. when do you go from version 1.0 to 1.1, or 1.5 or
even 2.0?
================
Yes...
Consistency and constant enforcement.
Consistency because any system can be understood by most as long as you
don't change boats in mid-stream, and what's tougher, enforcement because
it's so easy when you are rushed, and it's crunch time, to try to slide a
set of changes through with the thought "I'll fix it when I have time.",
which you won't have and which you'll forget.
My personal preference is that each time a polished version gets submitted
to the user, that becomes x.0 and all interim drafts are dot versions, but
some PMs around here insist that when the project is FINISHED (a project
could take three years), it gets 1.0 and all versions prior to that are dot
versions.
John Posada
Special Projects; Information Technology
Barnes&Noble.com
NY: 212-414-6656
****************************************************************************
**********************************
This electronic mail message contains information that (a) is or may be
CONFIDENTIAL,
PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE,
and (b) is intended only for the use of the addressee(s) named herein. If
you are not an
intended recipient, please contact the sender immediately and take the steps
necessary to
delete the message completely from your computer system.
Not Intended as a Substitute for a Writing: Notwithstanding the Uniform
Electronic Transaction
Act or any other law of similar effect, absent an express statement to the
contrary,
this e-mail message, its contents, and any attachments hereto are not
intended to represent
an offer or acceptance to enter into a contract and are not otherwise
intended to bind
this sender, barnesandnoble.com llc, barnesandnoble.com inc. or any other
person or entity.
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or view a live demo at: http://www.ehelp.com/techwr-l3
---
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.
