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.
0.0.1 is the first file saved by the softies. When the implemented features
work, this becomes 0.1.0. Then more features get added, 0.2.0
Then all the required features for the first release are ready, it goes into
QA, as (for example) 0.8.3
If this is the first iteration through QA, the internal number used by the
QA team becomes 0.8.3.1. Assume this gets rejected. Fixes are applied and
the new 0.8.3.2 gets released to QA. If this is accepted, it leaves QA as
0.8.3
Now, the product manager gets to accept it. If he does, the Release number
gets incremented.
Version 0.1 is now ready for beta. Version numbers get updated, and software
"burnt" and distributed.
The results of the beta come back - not usable.
So the softies get 0.1.0 to save next time as 0.1.1. They end up with 0.1.3
which goes to QA. QA needs two passes, meaning 0.1.3.2 gets turned into
0.1.3 ex QA into Product Mgr. He accepts, 0.2 is released. This passes Beta
etc. 1.0 gets released.
------- NEW STAGE -----------
If new functionality is added, but the architecture doesn't change, future
releases will be 1.1, 1.2 etc. At some point the increase in functionality
will drive an architecture change, to force version 2.0 etc.
Steve Hudson
Lead Technical Writer
Wright Technologies (Aus)
steve -at- www -dot- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!
-----Original Message-----
From: bounce-techwr-l-62124 -at- lists -dot- raycomm -dot- com
[mailto:bounce-techwr-l-62124 -at- lists -dot- raycomm -dot- com]On Behalf Of Mike
Sent: Wednesday, 28 March 2001 04:14
To: TECHWR-L
Subject: determining document version
Did some searching for this topic in the archives, but
didn't come up with anything. At which point do you
determine that your document has moved to a different
version? For example, when do you go from 3.3 to 3.4,
or from 3.3 to 4.0? Is there a set of standards that
has been published somewhere?
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available 4/30/01 at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
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.
