In a meeting today between Release Engineering, QA, and various team leads, we decided to enact a 7 day slip of the Fedora 11 release date. The primary reason behind this slip is the state of our blocker bug: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11Blocker&hide_re... We cannot begin Release Candidate phase until the blocker bugs are closed or at least in MODIFIED state. We are not there today, which would be our last day to enter RC phase and still have enough time to release on the 26th. We hope to enter RC phase in the next couple days, and hit our new target, June 2nd.
Freeze breaks for critical bugs will still be accepted, however trivial bug fixes should be pushed as updates via bodhi. Thanks!
Jesse Keating said the following on 05/19/2009 02:29 PM Pacific Time:
In a meeting today between Release Engineering, QA, and various team leads, we decided to enact a 7 day slip of the Fedora 11 release date. The primary reason behind this slip is the state of our blocker bug: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11Blocker&hide_re... We cannot begin Release Candidate phase until the blocker bugs are closed or at least in MODIFIED state. We are not there today, which would be our last day to enter RC phase and still have enough time to release on the 26th. We hope to enter RC phase in the next couple days, and hit our new target, June 2nd.
Freeze breaks for critical bugs will still be accepted, however trivial bug fixes should be pushed as updates via bodhi. Thanks!
Detailed schedules have been updated to reflect this change and some additional events:
1) Final GA Blocker Bug review meeting on Friday, 2009-05-22 2) "Go/No-Go" Meeting on 2009-05-26 @ 3 PM EDT
http://poelstra.fedorapeople.org/schedules/f-11/f-11-releng-tasks.html
John
devel-announce@lists.fedoraproject.org