TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>
> when do you make the last changes to the
> documentation? Take into account
> that there is not code freeze where I work. When do
> you say no more changes
> to be done?
>
What's a code freeze? Is that some kind of mythical
beast like the manticore or the jobsecurity?
I've never worked anywhere at which I *could* say "no
more." Every place I've ever worked, I've been
required to document any changes the
developers/engineers make, and they were free to make
any changes they wanted right up to the very last day.
I've worked on projects where I had to change screen
caps and all the writeups that went with them, both in
the online help and in the printed docs, on the very
same day that the final build was supposed to be done.
More than once I've been in a situation where the
build is supposed to be started 8 AM, and I had to
work the entire night before and didn't finish posting
my changes until 7:30 AM.
