On Mon, May 2, 2011 at 7:52 PM, Happy-melon happy-melon@live.com wrote:
If a feature freeze is to work, it has to either a) be for a very short period so that developers neither get disenchanted and wander off nor start stockpiling working-copy changes to empty onto trunk once it's thawed, or b) be part of a fundamental change in the way we approach rewrites. It would be perfectly acceptable to move to a completely different paradigm where branches are used properly, regularly reviewed, get plenty of inter-developer testing and can be smoothly merged back into trunk in an organised fashion. But right now, the only way to reliably get external eyes on code is to put it in trunk; the occasions when multiple developers are working on the same branch are both rare and not quite the same thing.
I'm proposing (a). Shifting to (b) is an organizational shift, and some people don't seem to think it can happen unless we move to the Magical World of Git.
-Chad