Erik, > As the RM for this release I tend to lean towards NOT adding features > to the 'release' branch after it has been cut, and to commit bug fixes > to the 'release' branch.
I follow this same model myself. The 'release' branch is considered untouchable for the most part during a RC period, only taking critical bug fixes deemed as blockers. Anything else is considered a known issue to be addressed in a later build. Immediately following a critical bug fix in the release branch, I immediately merge it back into develop to clear the bug also for my testers and anyone who may be working on a new feature in develop. So I for one lean towards that method. Chris On Tue, Dec 2, 2014 at 9:50 AM, Tom Chiverton <t...@extravision.com> wrote: > On 02/12/14 13:59, Erik de Bruin wrote: > >> As the RM for this release I tend to lean towards NOT adding features >> to the 'release' branch after it has been cut, and to commit bug fixes >> to the 'release' branch. >> > This. > By cutting off the release branch, you are stating the features in that > release. Bug fixes only at that point, surely ? > > Tom >
