Fedora 17 Change Freeze

Tim Flink tflink at redhat.com
Tue May 1 23:34:04 UTC 2012

On Wed, 2 May 2012 00:01:23 +0100
Ian Malone <ibmalone at gmail.com> wrote:

> On 1 May 2012 19:30, Dennis Gilmore <dennis at ausil.us> wrote:
> > 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

> 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

The process for marking bugs as release blockers or NTH is documented
 - 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120501/1b5e8c62/attachment.sig>

More information about the devel mailing list