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: Getting Code Changes Into Documentation From:yvonne -at- SMARTSTAR -dot- COM Date:Mon, 10 Apr 1995 08:59:24 -0700
MacGyver asked:
> How do you find out what software changes affect the documentation?
In addition to methods mentioned by others, I get a mail message about
software changes every day. This happens automatically, because our
programmers use code control software that prompts them for a description
of the change and the problem # in our bug tracking system for the change.
Every night, an automatic procedure gathers all the comments and sends the
list of changes as e-mail to all the programmers. All I had to do was ask
to be added to the mailing list.
Of course, their comments aren't always all that clear. But with practice,
I've learned which types of changes are likely to affect the documentation.
