Greetings folks,

Just a quick update on the status of F13Blocker.  According to the
schedule [1], Fedora 13 is scheduled to enter the release candidate
phase *today*, May 6, 2010.  In order to enter this phase, all OPEN
F13Blocker bugs must be in MODIFIED or ON_QA.

The numbers are certainly moving in the right direction.  Thank you all
for being on top of your bugs.  There are now only 4 OPEN (NEW +
ASSIGNED) issues remaining (see list below).

To get a bug off the list, you can ...
     1. Resolve the issue as desired (followed by a build and F13 bodhi
        update)
     2. Prove there is minimal, or no, impact to the Fedora Release
        Criteria [2]

Use your last minute analogy of choice (end game, final lap, eleventh
hour, don't cut the blue wire (just seeing if you're paying attention)).
Today is the scheduled date for creating the Fedora 13 release
candidate.  Any delays in creating the release candidate put Fedora 13
at risk for a 1 week slip.

Thanks,
James

[1]
http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html
[2] https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria

= anaconda = 
      * 571900 (mgra...@redhat.com) NEW - Keyboard mapping not correct
        (USA instead of Belgium) when first login after install Fedora
        13 Alpha - 
      * 588597 (anaconda-maint-l...@redhat.com) NEW - "DeviceError:
        ('device has not been created'

= kernel = 
      * 587171 (a...@redhat.com) ASSIGNED - Intel kms leads to an all
        black display

= preupgrade = 
      * 587627 (rich...@hughsie.com) ASSIGNED - Kickstart file is not
        generated when no space for install.img

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to