This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Active release branches
On 8/22/2012 12:07 PM, Joseph S. Myers wrote:
> On Wed, 22 Aug 2012, Carlos O'Donell wrote:
>
>> I think 2.11 to 2.14 are now closed.
>>
>> Is it important to mark a branch as open or closed?
>>
>> What do we gain from this categorization?
>
> Listing a branch as active when it's not active is misleading to users.
> Active branches should, for example, get backports of security fixes and
> serious regression fixes.
>
> If a branch is closed then bugs requesting a backport to it can be closed
> - or bugs requesting backports to multiple branches can be closed once the
> backport is on the active branches (bug 14287 may be the only currently
> open case, with both glibc_2.14 and glibc_2.15 keywords).
>
Those all sound like good reasons to me.
I've update Release/2.13 to indicate it was closed on 2012-08-22.
I've updated Release, removing 2.13 from the list of supported branches.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026