Re: 2.11.1: Call for testing

[Roland McGrath <roland at redhat dot com>]

As per the original concept of release branches, there shouldn't be a
release next week just because you'd like to.  A community minor release
comes only from a consensus of distro libc maintainers who have already
been using the code in production or beta testing.  Not that you
shouldn't like to push the process and prod all distro maintainers.  
But IMHO this process is only really useful at all if it's based on
consensus of manifest use in distro packages (more than one independent
distro), rather than on a single honcho's preferences and deadlines.

Fedora 12 is using 2.11 so I know at least Andreas should be on board
before any decisions are made about point releases.

This is the first round of this process and the plan for it has always
been rather vague.  Now is the time to grow some more wiki pages about
what the procedures are, and have discussion and consensus on what they
should be.  Some details will always differ by the preferences of the
particular branch manager, and that's fine.  But let's get started on
setting the general guidelines for how this will go in every cycle.


Thanks,
Roland