On Mon, Mar 5, 2012 at 4:25 PM, Georg-Johann Lay <a...@gjlay.de> wrote:
> Richard Guenther wrote:
>> All commits to the 4.7 branch need explicit release manager approval. AVR
>> isn't primary/secondary so please do not change anything before is
>> released 4.7.0 for it.
> What is the exact procedure in that case?
> Wait until approve from release manager in that case?
> Who is the release manager, and should I CC for such changes?
> Or just hope the patch is not overseen.
The exact procedure is to do bugfixing during stage3/4, for release blockers
that pop up after a release candidate is created (like now), CC a release
manager (Jakub, me, Joseph) for patches that you like to get in even
though the branch is frozen. Usually only bugs that prevent basic functionality
(like building a target) can be fixed at this point, for everything
else you have
to wait until after 4.7.0 is released and the branch opens again for regression