Re: Branching PHP6

Hi! > By release branch, are you referring to minor releases or maintenance > releases? If the latter, it'd be a moot point under this model because > we'd be getting rid of separate branches for maintenance releases > altogether. Instead, the RM would simply apply the tag to the commit where > they want the maintenance release to occur. That would be a much cleaner > approach than what we're doing now. It is not. Especially not when we have many people that can commit code in any moment. RM should be able to create a stable release branch and do all the release work in this branch knowing it is not going to change, it can be verified, and it can be amended with urgent fixes (or, sometimes, removing certain changes) without having to pull in all the delta of unverified code that happened in between. Tags are not meant for that, release branches are meant exactly for that. I see absolutely no reason why what we are doing now is in any way "unclean". -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227