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.
For our mainframe manuals, which rev fairly often, we use a part number on the cover that references the revision, so it looks like this: <product_number>VxxxRxxxx (I personally hope we never get to four digits between versions, but they're there if we need them). I also slap a date on the copyright page (p2) for each PDF.
Those seem to work for our tech support staff.
Mike McCallister
Senior Document Architect
PKWARE, Inc.
648 N. Plankinton Avenue
Suite 220
Milwaukee, WI 53203
Direct: 414-289-9788 x1136
www.pkware.com
-----Original Message-----
From: techwr-l-bounces+mike -dot- mccallister=pkware -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+mike -dot- mccallister=pkware -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of M -dot- Vina-Baltsas -at- mindray -dot- com
Sent: Wednesday, December 07, 2011 10:38 AM
To: Julie Stickler
Cc: techwr-l-bounces+m -dot- vina-baltsas=mindray -dot- com -at- lists -dot- techwr-l -dot- com; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Revision control
This cracked me up, "But that mostly works if your company follows a logical release numbering system..." We don't always have a logical release schedule. We DO try but it doesn't work out that way. We ship when the software testing is finished and our bugs are at a minium! ;-)
I can add the rev and SW version to our revision page but am not sure how to handle the maintenance releases/patches, etc. For example, something like "Version 2.3, 2.3.1, 2.3.2" might work, right?
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-