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?
If there is no code freeze, when do you ship?
Else, you take a day or two after they cut the release
build, make sure you've hit everything, send it off to
be published (however you do that - internally
electronically and/or externally via press), and then
keep on writing as they continue to code for the next
release.
=====
Goober Writer
(because life is too short to be inept)
"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
-- Geoff Hart
We can't all be as creative with sigs as krautgrrl. ;-)
