Proposed adjustments to our release cycles

[Marco Martin]

On Saturday 16 June 2012, Shaun Reich wrote:
> 
> and the freezes would have to be *very* well communicated, because
> even now we run into issues with people not realizing that we're in
> string freeze or feature freeze.

a part of the plan (kindof a consequency in the long term of the thing 
described here) is that it would mean aiming to a state where there are nover 
freezes (or well, master is always frozen, depends how you look at ;)

master should always be in a releasable state, while the feature branches are 
merged in an integration one before is well tested.

now of course there are a lot of technical details how work out this, like how 
to manage translations

Cheers,
Marco Martin