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.
Subject:Re: Revision control From:Gene Kim-Eng <techwr -at- genek -dot- com> To:M -dot- Vina-Baltsas -at- mindray -dot- com Date:Wed, 7 Dec 2011 09:00:49 -0800
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)
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-