Re: Revision control

[Gene Kim-Eng <techwr -at- genek -dot- com>]

Every maintenance release or patch rolls the SW to a new build number.  We
use a three-stage numbering scheme (x.x.x), where the third x is patches.
Patches are usually documented in service bulletins, which are accumulated
and implemented in the manuals with major (first x) or minor (second x)
releases.

Gene Kim-Eng


On Wed, Dec 7, 2011 at 8:50 AM, <M -dot- Vina-Baltsas -at- mindray -dot- com> wrote:

>
> Since you put this information in your footers and covers, how do you
> handle the verbiage for maintenance releases or patches?
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://www.doctohelp.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com