You do not have to make an announcement, but people generally have asked for a freeze around a major merge so that problems from the new functionality can be pinpointed and merge conflicts can be avoided.
David On Fri, Jun 12, 2009 at 9:49 PM, Aldy Hernandez<al...@redhat.com> wrote: > On Sat, Jun 13, 2009 at 01:51:42AM +0100, Dave Korn wrote: >> Aldy Hernandez wrote: >> > Hi folks. >> > >> > At the last minute Ian got a patch in that touched a bunch of places >> > that I was also changing. I resolved the conflicts, and bootstrapped >> > and tested for C and C++. Unfortunately, people kept committing stuff >> > that caused conflicts, so I broke down and committed after a minor C/C++ >> > bootstrap. >> >> Did you tell anyone that you were merging a branch to mainline? I honestly >> didn't see an announcement. (Is there any reason why you shouldn't have >> requested a freeze?) > > The branch was approved by a GWP, I didn't know you needed to make a > special announcement. > > I will be fixing any regressions shortly. >
