Sounds like a code freeze/thaw. What are the conditions for a *major* PR? Even a minor PR could introduce major bugs. I will point out that you have the option of cherry-picking specific new patches on top of the 0.1.0-rc3 tag to create a new rc. This ensures that 0.1.0 only includes changes that were tested in the previous rc's plus specific critical fixes. This is how Mesos handles patch releases (e.g. 0.23.0 -> 0.23.1) or release candidates after the first. Cut the rc0/1 from HEAD, then cherry-pick on top for all future rcs.
On Mon, Nov 30, 2015 at 12:42 PM, Santosh Marella <[email protected]> wrote: > Hello All, > > As we are in the middle of IPMC voting to release myriad-0.1.0, I request > the committers to hold off merging any *major* PRs to the "master" branch. > > The current RC has been tested well for the features that went into it. > Just in case we receive more feedback from IPMC, we want the "master" > branch to stay as close to current RC as possible so that when we cut a new > RC with IPMC's feedback, we don't need to worry too much about the > stability of the new RC. > > Thanks, > Santosh >
