I think is all a matter of how much input do you want?
Indeed. A build at some preset time, be it nightly or weekly, is not necessarily the best approach. I think after any significant change is made (as decided by the need to receive feedback on it) then a new build can be produced. Change this section to "Latest Build" and only release as necessary, when necessary. It may be daily during some periods, it may take five days or it may even happen twice in the same day if something warrants it. Either way, we'll live.
I second this suggest with some additional ideas.
Change "Nightly Build" section to "Latest development Build".
And, I suggest the idea "Latest Test Build" being used on the Wiki page somewhere this would refer to a "Development Build" that was found to work up to some set level of performance.
Some items that a "Latest Test Build" should have.
Builds for it exists for Linux, Windows Unicode and Windows ANSI.
Linux builds should exist for a least
Linux platforms.
The "Latest Test Build" should be able to build Code::Blocks using SVN setup.
Once, Code::Blocks 1.0 is released I would stop "Latest Test Build" until the "Release build" (Code::Blocks 1.0) can NOT build the "Latest development Build" anymore.
Note, I am thinking of "Latest Test Build" being used as a bootstrap build that can build C::B from SVN or at some future time from tgz.
Tim S