Closing old release branches

[Joseph S. Myers]

On Wed, 28 Aug 2013, Roland McGrath wrote:

> Let's consider this for a policy:
> 
> At the same time we choose the release manager for an upcoming release, we
> take a poll on the status of past release branches.  For each past release,
> if its release manager does not respond within a week, or says they are not
> really maintaining it any more, then we give another week for someone new
> to step forward and say they want to maintain that release branch (and
> perhaps say why they care).  After that, we declare each orphaned branch to
> be closed, and update the wiki.
> 
> For the current cycle, we can start that process now since we didn't do it
> when selecting the 2.18 release manager.

I've seen no sign of release manager interest in continuing to maintain 
the 2.16 and older branches.  Is anyone else interested in them?

-- 
Joseph S. Myers
joseph@codesourcery.com