Page History

...

• When the x.y release is being prepared, master will be “frozen” for new features. The release managers decide what goes in and what not.
• Working on new features will continue in feature branches, that can be easily rebased against master since it is stable and only receives bug fixes. The easiest would be to work on a feature branch in your own fork, although committers may choose to maintain a feature branch at the Apache CloudStack git repo instead.
• The time master is frozen should be as short as possible. It would be awesome if we could reach a schedule where master is open the first half of a month, and frozen the second half. Or even open for 12 days and then frozen for a weekend.  But let's first try this and see how it works. We'll be able to speed it up as we go.

...