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: David Miller <davem at davemloft dot net>
- To: carlos at redhat dot com
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 18 Dec 2014 11:58:22 -0500 (EST)
- 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>
From: "Carlos O'Donell" <email@example.com>
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.