On Tuesday 09 July 2013 16:12:35 Andras Mantia wrote: > I also find the motivation somewhat contradictory. Yes, you want to provide > new features faster, but by cutting down testing time. *Are you sure?* Well here we have to ask whether the current testing procedure works. Since the beta got released I have not been running master of the application I maintain. I'm developing ahead in custom branches and don't see a reason why I should switch back to master. I expect that many other developers work in a similar way. Not working ahead in a different branch, means sitting around and doing nothing or wait till a bug report gets in which could be fixed.
If you develop in a "always releasable master" way, the enforced testing period doesn't make any sense. As you say different projects have different development models. If you use master for your development then you need the stabilization time. If you develop in branches, maybe even with an integration branch step before going to master the testing period doesn't give you anything in addition to the larger audience. The testing period slows down the development. Since we are on git, I have started the development of the next release on the day the feature freeze took place. Cheers Martin
signature.asc
Description: This is a digitally signed message part.
