On May 17, 2016, at 8:19 AM, Sandra Loosemore <san...@codesourcery.com> wrote: > > I thought I remembered mail going by that changes to a release branch require > RM approval too.
For time to time, the RM can close any release branch at any time for any reason. :-) For example, a gcc 3.2.x release branch has been closed for any checkins. When they are trying to get a release out, they may say, no checkins til the release is made and so on. In general, they update https://gcc.gnu.org/ to list the state of each branch. The non-permanent closures are generally only til the next release. The permanent closures are because we are removing support for an old release because we have a new release now.
