That is correct - only changes we explicitly say should go in for a new RC should go into the release branch until we've actually got the release done.
A. On Fri, Dec 20, 2013 at 6:23 AM, Andrew Phillips <aphill...@qrmedia.com>wrote: > No, I want the changes in 1.7.x - I'll nuke the existing release-process >> commits and replace them with new ones. >> > > Sorry, yes, I should have added that this won't be a problem if we're > going to cut new RCs. I was just thinking that, in general, we should be > considering the release branch frozen (and not commit any changes to it) > while the release is in progress and until the release commits have been > pushed. > > Or am I missing something? > > Anyway, looking forward to RC2! > > ap >
