2.25 freeze - a little more than the holiday fortnight to go

[Joseph Myers]

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