Workflow for a release

["Zen C" <zenizenc -at- gmail -dot- com>]

Hi,

I am working on release note and have been working on it for two weeks.
While everything is finalized, sent to the responsible parties and suppose
to go out on Friday they come up with 6 new changes that I have to add to
the release notes and incorporate to the help. This has been the case for
the last 3 release I did and luckily this time my boss took her stand and
said that we need a cut off date for future releases. I am the only tech
writer for the company so everything else is on hold as I am editing the
documents a million times cos of all the GUI changes and new items they are
bringing in.

Does anyone one have a good work flow they follow, or a rough idea on what
the best cut off dates are. I know it depends on the company and a lot of
other factors, but it will be great if I can get some idea to suggest
something feasible.

Have a great day!

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- 

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%40web.techwr-l.com


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
http://www.techwr-l.com/ for more resources and info.