RE: Documenting incremental releases in a What's New

[David Farbey <David -dot- Farbey -at- lazysoft -dot- com>]

What Barb describes is exactly what I am doing this week for our forthcoming
release. The discussion with Engineering and Sales about what to highlight
in the "What's new" section is usually followed by the discussion with the
same folks about what problems need to be mentioned in the "Release notes".

David Farbey
mailto:david -dot- farbey -at- lazysoft -dot- com
Technical Writer
Lazy Software Ltd., UK
http://www.lazysoft.com
Phone: 01628-642314

-----Original Message-----
From: Barb Einarsen [mailto:barb -dot- einarsen -at- nettest -dot- com]
Sent: 08 July 2002 14:48
To: TECHWR-L
Subject: RE: Documenting incremental releases in a What's New



I would delete the 6.0 information and highlight the changes specific to
6.1 because: 
 * there is about 5 months between releases
 * the 6.0 information will be integrated into the guide and help
systems (I assume)
 * it honors the spirit of 'what's new'

Hope this helps,
Barb


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.