On Wed, 2 May 2012 00:01:23 +0100 Ian Malone <ibmalone@xxxxxxxxx> wrote: > On 1 May 2012 19:30, Dennis Gilmore <dennis@xxxxxxxx> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi all, > > > > the fedora 17 schedule > > http://fedoraproject.org/wiki/Releases/17/Schedule lists the final > > change freeze as 2012-05-07 this means that you need to make sure > > that any changes you want in Fedora 17 final must be submited for > > stable in Bodhi before 2012-05-07 there will be a small window on > > monday where you can get your build in still but it is not assured. > > after this time only blocker bugs will be accepted to be pushed for > > stable. please work on testing and ensuring anything you want in > > final has the appropriate karma. If you have questions please drop > > by #fedora-releng on freenode > > There are a number of preupgrade bugs not marked as blockers, what > happens to these? That depends on where the actual bug is, to be honest. If it's in the actual preupgrade package itself - that's in F15 and F16 and would not be affected by the F17 code freeze > https://bugzilla.redhat.com/show_bug.cgi?id=813973 This is a known limitation - workarounds are documented in the wiki http://fedoraproject.org/wiki/How_to_use_PreUpgrade#Not_enough_space_in_.2Fboot > https://bugzilla.redhat.com/show_bug.cgi?id=817383 > https://bugzilla.redhat.com/show_bug.cgi?id=817384 This is the first that I've heard of either of these - if you think they're worthy of being release blockers, feel free to mark them as such. The process for marking bugs as release blockers or NTH is documented at: - http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - http://fedoraproject.org/wiki/QA:SOP_nth_bug_process You can find the tracker bugs to block on this page: - http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers Tim
Attachment:
signature.asc
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
