This is the mail archive of the
mailing list for the glibc project.
Re: Only 23 days left of active development before master freezes.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: David Miller <davem at davemloft dot net>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 18 Dec 2014 15:37:58 -0500
- Subject: Re: Only 23 days left of active development before master freezes.
- Authentication-results: sourceware.org; auth=none
- References: <54919EC4 dot 6080205 at redhat dot com> <20141217 dot 232706 dot 2105415741987535741 dot davem at davemloft dot net> <5492EC78 dot 8000608 at redhat dot com> <20141218 dot 115822 dot 449516363418770634 dot davem at davemloft dot net>
On 12/18/2014 11:58 AM, David Miller wrote:
> From: "Carlos O'Donell" <firstname.lastname@example.org>
> Date: Thu, 18 Dec 2014 10:02:16 -0500
>> The freeze is only intended to prevent new features from being added
>> late in the development cycle.
>> Part of the freeze process for this release could include fixing all
>> targets to compile, and then test them.
>> This way we don't have new code going in last minute because I haven't
>> called a freeze.
>> Would that satisfy your requirements?
> You're simply creating a situation where people who work on said
> targets aren't going to get any meaningful work done because all
> they will be doing is fixing the build.
You are correct, you can't get meaningful work done until the
builds are fixed. That's what everybody is working on.
If you don't see the value in -Werror, then I can understand
why you're upset by the build breakage. Is this the case?
Do you need help fixing up sparc? Do you have a sparc box?
I can help.