|
|
z2007-04-18- Socialtext Release Management
|
|
Whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government, laying its foundation on such principles and organizing its powers in such form, as to them shall seem most likely to effect their Safety and Happiness.
|
|
(backlinks off)
|
(map off)
|
(search off)
|
|
last edited
by BillSeitz
on
Sep 2, 2008 1:40 am |
Social Text is sharing their [Release Management] process. It sounds like they have multiple [Project Team]-s each working on a ProJect, consisting of multiple [Feature Set]-s, each of which crosses Iterat Ion boundaries. And they only integrate when a [Feature Set] is going to be ReLease-d. We had maintained this myth that not branching would help us to maintain agility, but at the last minutes things always came up and we'd get into what seemed like infinite loops of wait states. Our not-so-decoupled as we'd like codebase didn't help this. So we decided it would be good to start more habitual branching but to do we knew, based on experience, that we would need some process formalization to ensure that branches would get tested and merged with alacrity.
(They also have the complexity of dealing with a Product Line.)
Bill Seitz, fluxent at gmail dot com, Weblog