This is the mail archive of the
mailing list for the glibc project.
Re: v2: The GNU C Library 2.16 release plan
- From: David Miller <davem at davemloft dot net>
- To: joseph at codesourcery dot com
- Cc: carlos_odonell at mentor dot com, libc-alpha at sourceware dot org, aj at suse dot com, eggert at cs dot ucla dot edu, ryan dot arnold at gmail dot com, hjl dot tools at gmail dot com
- Date: Thu, 31 May 2012 01:35:38 -0400 (EDT)
- Subject: Re: v2: The GNU C Library 2.16 release plan
- References: <4FAC3FCE.email@example.com><Pine.LNX.firstname.lastname@example.org>
From: "Joseph S. Myers" <email@example.com>
Date: Thu, 31 May 2012 00:13:31 +0000 (UTC)
> Three weeks seems a more practical time for architecture maintainers in
> libc and ports to ensure their architectures are up to date and have good
> test results not indicating architecture-specific problems. Here freeze
> needs to be understood in terms of avoiding any patches likely to need
> per-architecture updates (even if those updates are mechanical) or
> involving risk of per-architecture breakage more than avoiding changes in
> other areas of glibc.
I agree with Joseph, especially given the fact that we have people
who have to check multiple targets.