canmove, Confirmed users
2,056
edits
(initial draft) |
No edit summary |
||
| Line 69: | Line 69: | ||
(An alternative plan of four weeks of development, four weeks of alpha->beta stabilization, and four weeks of beta->release stabilization, with the alpha->beta stabilization split across the branches, would give us a 4/8 ratio, but it would mean branch controls for the last two weeks of each cycle on dev.) | (An alternative plan of four weeks of development, four weeks of alpha->beta stabilization, and four weeks of beta->release stabilization, with the alpha->beta stabilization split across the branches, would give us a 4/8 ratio, but it would mean branch controls for the last two weeks of each cycle on dev.) | ||
= References = | |||
* [http://thinking-in-code.blogspot.com/2010/07/train-model-of-software-development.html Train Model of Software Development] | |||
* [http://pauljulius.com/blog/2009/09/03/feature-branches-are-poor-mans-modular-architecture/ Feature Branches are Poor Man's Modular Architecture] | |||