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 10:02:16 -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>
On 12/17/2014 11:27 PM, David Miller wrote:
> From: "Carlos O'Donell" <firstname.lastname@example.org>
> Date: Wed, 17 Dec 2014 10:18:28 -0500
>> We have 23 days of active development before I freeze master for 2.21.
>> If you object, please speak up now.
> I don't think we should set a freeze or release date until the tree
> even builds for all targets again after the -Werror addition.
> Some targets have been known to be broken for weeks.
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?