RE: meaning & practice of a "doc freeze"

["Bill Swallow" <wswallow -at- nycap -dot- rr -dot- com>]

Do whatever makes sense.

We have a "content freeze", which means no new info going into the book. We
have reviews along the way, so there are no surprises a week before content
freeze. When we freeze content, we mean NO ONE adds info to the book - it's
done. However, the book can still be proofread for grammar, spell-checked,
and then set up for publishing. We publicize the dates at the beginning of
the project, and go from there. If the project slips or is pulled in, the
documentation dates move as necessary.

But, you as the lead writer on the project need to hold firm to your dates.
They may want to add info, but you need to make it clear that they cannot do
so without slipping the publishing date. If they are OK with that, then so
be it.

Bill Swallow
wswallow "at" nycap "dot" rr "dot" com 

::: -----Original Message-----
::: So my question is, once you have produced a "final" after 
::: the freeze date, 
::: do you then submit the final back to the SMEs or 
::: developers?  I ask because 
::: if I do this, they still want to make changes. 



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

ROBOHELP X5 - ALL NEW VERSION!!

Have you tried the latest in Help Authoring from RoboHelp?
Try ROBOHELP X5 for Free - Now with Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more!

Download a free trial today: http://www.ehelp.com/techwr-l4

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -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.