This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: 2.25 freeze - a little more than the holiday fortnight to go
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, Carlos O'Donell <carlos at redhat dot com>
- Date: Wed, 21 Dec 2016 21:18:21 +0000
- Subject: Re: 2.25 freeze - a little more than the holiday fortnight to go
- Authentication-results: sourceware.org; auth=none
- References: <10ea30d2-2942-e4c1-8399-2d5d3288211d@gotplt.org>
I'm dubious about keeping piling on "blockers" without evidence that there
are actually people to review the patches no later than 31 December
(earlier than that if revisions and re-review are needed). I think
listing something as a blocker should require the listing to name a
reviewer who has committed to reviewing the patch by a specified date
(where that date must be before the freeze, i.e. no later than 31
December, for any significant architecture-independent patch; patches to
architecture-specific code might have slightly later dates if the people
testing on that architecture are happy with the reduced stabilization
time). If the review is not forthcoming on time or any required revisions
are not ready, reviewed and committed no later than 31 December, the
expectation should be that such a patch is postponed.
We should expect 1 January onwards to be available for architecture
testing and stabilization / bug fixes, so avoid any significant changes
after then that would require redoing such testing.
--
Joseph S. Myers
joseph@codesourcery.com