This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Rolling master branch
- From: David Miller <davem at davemloft dot net>
- To: siddhesh dot poyarekar at gmail dot com
- Cc: law at redhat dot com, siddhesh at redhat dot com, libc-alpha at sourceware dot org
- Date: Mon, 29 Sep 2014 13:40:02 -0400 (EDT)
- Subject: Re: Rolling master branch
- Authentication-results: sourceware.org; auth=none
- References: <20140929082252 dot GB2217 at spoyarek dot pnq dot redhat dot com> <54295333 dot 8040205 at redhat dot com> <CAAHN_R3ki6T08PVXOOUr3TEDAusBKiCf_O_Si1ZEp+HjvBsWug at mail dot gmail dot com>
From: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Date: Mon, 29 Sep 2014 20:39:05 +0530
> On 29 September 2014 18:10, Jeff Law <law@redhat.com> wrote:
>> What we've found in GCC-land is it gets really hard to focus engineers
>> efforts on fixing the important bugs to get a release out the door. Most
>> folks would rather continue their work on features, optimizations, etc
>> rather than fix bugs. The nerve :-)
>
> The problem seems a bit different with glibc. Master branch freezes
> seem to shift focus from glibc to other projects since most
> contributors to glibc usually work on other parts of the toolchain
> too.
That's fine, because this means they won't be adding destabilizing
changes to the glibc release branch either.
I think we must cut off new feature development during the freeze
because indirectly and directly allowing people to install new
features in parallel takes resources away from the release and
stabilizing process.