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: Version Release Notes From:Chet Ensign <censign -at- INTERSERV -dot- COM> Date:Sat, 25 Jan 1997 13:32:40 -0800
Rebecca also asks:
>> For those of you who write version release notes, do you refer back to
the parts of the manual affected in the release notes themselves? Do
customers find this helpful? Distracting? Do you think it's a good idea? <<
We sometimes had to do this. Again, I don't remember anyone ever objecting to
it. I personally find it useful.
You didn't ask about implementation, but implementing change bars and
cross-refs like this and maintaining them took a lot of work. If I remember
correctly, we never did get it automated, and the problem is then that putting
the bars in, taking them out, etc. becomes a lot of tech writer's time that
could be spent on content.
Chet Ensign Office: 212-448-2466
Manager of Data Architecture Home: 201-378-3472
Matthew Bender & Company, Inc. Email: censign -at- bender -dot- com
New York, NY