RE: Troubleshooting Vs Release Notes

Subject: RE: Troubleshooting Vs Release Notes
From: "Wroblewski, Victoria" <vwroblewski -at- NECsphere -dot- com>
To: Sion Lane <slane -at- ubq -dot- thrupoint -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 31 Jan 2012 09:12:03 -0600

-----Original Message-----
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.

- V

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.

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Troubleshooting Vs Release Notes: From: Sion Lane

Previous by Author: RE: Techno-fuddyduddy getting anxious
Previous by Thread: Troubleshooting Vs Release Notes
Next by Thread: Re: Troubleshooting Vs Release Notes

What this post helpful? Share it with friends and colleagues:

Sponsored Ads