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.
It is my first time working on release notes and from all the samples I have
had a chance to look at online, I realized that what it should include is a
brief description of what is changed and you redirect the user to the help
file for more detailed information. Am I right or wrong?
The person reviewing my release notes came up with this suggestion.
Add screen shots for items that have one. For example if printing options
are changed for something, explain the way it is done and add screen shots
as it would be in the help file. I know you point them to the Help system,
which is great, but they are lazy.
Any suggestions on this comment ? Do release notes usually go out with a lot
of details or is a brief outline of what is changed only?
Please send me your comments.
Thanks,
Zen
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-