Re: release process with git

Hi! > release candidates. I mean, we're still planning on having multiple > release candidates before an actual release, right? If so, then Not if we can avoid it. If we don't have critical bugs in RC1, we release it. > obviously we'll need a way to commit those changes. If they're not made > on the RC branch, then where were you thinking they should go, and how > would we then apply those bugfixes to the 5.4 trunk if not through a merge? If you have bugfix for 5.4, commit it into 5.4. If it's critical for current release, it will be pulled by RM into the release, otherwise he automatically becomes part of the next release. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227