"According to Erik Troan, vice president of product development
at Red Hat, the company was caught between the need to innovate,
meet deadlines, and provide a stable platform. "We were in a bind,"
Troan said. "We plan our releases well in advance, and we've
delivered releases at regular intervals for many years." He added
that a number of new glibc features, such as support for 16-bit
languages and multiple hardware platforms, justified breaking some
compatibility. "With Red Hat 7, we decided it was the right time to
hurt forward compatibility in order to move to the next
"Red Hat 7's version of glibc hasn't been cleared for production
use by the glibc maintainers at the GNU project. The GNU web page
on glibc insists its most current stable release is 2.1.2 -- older
than the version already running in Red Hat's 6.2 package."
"The fact that the GNU page doesn't appear to have been
updated in a year makes one wonder whether it's the definitive
source of glibc progress reports and stability information.
Release information for glibc is all over the place. The GNU FTP
site doesn't go past 2.1.91. Debian's "stable" version is 2.1.3 and
its "unstable" one is at 2.1.94. And the freshmeat listing for
glibc says 2.1.3 for production version and nothing for the