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.
From: Sion Lane
Sent: Tuesday, January 31, 2012 8:58 AM
At the moment, I'm working on the theory of 'if it only happens sometimes/on some devices/on some configurations, it goes in Troubleshooting' and 'if it always happens whatever you do or whatever you're using, it goes in the release note'.
Anyone got any better ideas?
Release Notes = We think we can fix this, or we made the problem that causes it.
Troubleshooting = This is how we designed it.
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-