From Fedora Project Wiki

Revision as of 01:07, 11 February 2010 by Jkeating (talk | contribs) (Update with progress)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page tracks the actual implementation of the No Frozen Rawhide (NFR) Proposal.


  1. Install images are no longer being created for rawhide.
    • To install rawhide follow the instructions at: FIXME
    • Links to public announcements: FIXME
  2. Bodhi modifications have been made (details & patch), deployed to staging, and tested
  3. Mash tested and confirmed to have the ability to create two trees at the same time in our infrastructure
  4. Communicated new layout to the mirrors
  5. Worked out location to hold test images of rawhide and last known good
  6. New paths primed on master mirror via hardlinks
    1. buildrawhide script updated to keep hardlink paths updated until freeze
  7. <insert other things that are done>


To implement for Fedora 13, all of the following must be accomplished by Alpha Freeze (currently scheduled for 2010-02-16).

  1. Create buildpendingtree script to compose the branched content each night
  2. Create a single rsync script to run after both buildrawhide and buildpendingtree are done
  3. Deploy new bodhi code into production
  4. Update fedora-release(-rawhide) for new paths
  5. Turn on mirrormanager for new paths

Implementation Plans

  1. Continue to produce rawhide as a repo of packages without install images
  2. At alpha freeze, branch CVS for F-13
    • devel/ now builds for F-14, reflect that in fedora-release and koji
  3. rawhide builds are published to pub/fedora/linux/development/rawhide/
  4. F-13 builds are published to pub/fedora/linux/development/13/
    • Potential F-13 builds are published to pub/fedora/linux/updates/testing/13/ either nightly or as part of standard updates pushes.
  5. Bodhi will be used for managing builds from F-13. Push to testing goes to the updates-testing location. Push to stable goes to the development/13 path.
  6. Install images created in the development/13 path.
  7. Packages in the critical path will require positive karma from releng or qa before allowed to go stable. Packages outside the critical path will be managed just as updates are now.
  8. At F13 Release Candidate stage, pushes to "stable" will go to pub/fedora/linux/updates/13/ instead of the Everything/ path. Release blocking fixes will be pulled into Everything/
  9. Packages will be signed as part of the updates process, as well as "automatically" as builds happen

Unfinished Tasks

  1. Collect links to all rawhide pages on the wiki
  2. Rework all wiki pages describing rawhide to reflect NFR
  3. Public announcement blitz about no rawhide install images for Fedora 13

Unresolved Questions & Topics

  • What do we call the pending release tree?
  • How are buildroot overrides handled, freeze break needs vs 0-day update needs
  • Increased number of "double" commits (things committed to rawhide, and duplicated on the release branch)
  • Relies on updates-testing to drive feedback for freeze breaks, and updates-testing is not as well used as it could be.
  • Division of our testers between rawhide and the pending release
  • Are we now Debian (Unstable, testing, stable)
  • Potential to break chain-builds even more depending on when we force things through bodhi