RE: Release notes and readme files

["egalite" <egalite -at- westnet -dot- com -dot- au>]

Excellent points, thank you!

(and nice tie-in with development processes, something I find is a problem
in many companies, big or small)

Trish :)

Steven Jong wrote:
: When writing release notes/readme files, one important 
: distinction to  
: make is between bugs found by customers and bugs found during  
: testing. The former should wind up in the release notes in one of  
: three places: if it was fixed, as a bug that's been fixed; if it  
: hasn't been fixed yet, as a known issue; if it's not going to get  
: fixed, as a clarification.
[snip] 
: If after discarding "virtual" bugs you still have a 
: substantial list,  
: you have a problem with your development process, not your release  
: notes.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WebWorks ePublisher Pro for Word features support for every major Help 
format plus PDF, HTML and more. Flexible, precise, and efficient content 
delivery. Try it today! http://www.webworks.com/techwr-l

Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com


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

Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.