The new code freeze date will be decided at next Wednesday's Gecko
1.9 status meeting, and it will be set somewhere between October 24th
and October 31st depending on our blocker fix rates. In the meantime,
the tree remains at threat level "orange" (always see the tinderbox
 for the current checkin rules) where only patches on blocking
bugs and those with driver approval are allowed to be checked in. All
contributors and drivers should be limiting risk, and testing their
patches for memory leaks and regressions before committing them, then
watching the tree afterwards to see the effects.
Once the new code freeze date is finalized, it will be announced on
Mozilla Developer News and in the mozilla.developer.planning
newsgroups. At that time we'll also announce the date when the tree
will move to threat level "red", where all checkins must be given
explicit endgame driver approval in order to limit risk of regression.
I think you wanted
Should we come up with a new term for this other than freeze? I
think the current usage is confusing, because what we used to call
"freeze" is now called "red", and we're reusing the term "freeze"
for something even more frozen. Maybe, instead of reusing the term,
we should come up with another one, so that people don't interpret
the term "freeze" with the old meaning? (maybe a color? black?)
As a bonus you might use labels that actually described the character of
the state of the branch. Even acronyms would be better than threat