No Frozen Rawhide Implementation
This page tracks the actual implementation of the No Frozen Rawhide (NFR) Proposal.
- Install images are no longer being created for rawhide.
- To install rawhide follow the instructions at: FIXME
- Links to public announcements: FIXME
- <insert other things that are done>
To implement for Fedora 13, all of the following must be accomplished by Feature Freeze (currently scheduled for 2010-02-09).
- Bodhi retrofit work done for sure before Feature Freeze
- Mash enhanced with ability to create two trees at the same time in our infrastructure
- Communicate new layout to the mirrors
- Continue to produce rawhide as a repo of packages without install images
- At feature freeze, branch CVS for F-13
- devel/ now builds for F-14, reflect that in fedora-release and koji
- F-13 builds are published to pub/fedora/linux/releases/13/Everything/nightly
- Potential F-13 builds are published to pub/fedora/linux/updates/testing/13/ either nightly or as part of standard updates pushes.
- 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 Everything/ path.
- Install images created in the Everything/ path.
- 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.
- 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/
- Collect links to all rawhide pages on the wiki
- Rework all wiki pages describing rawhide to reflect NFR
- Public announcement blitz about no rawhide install images for Fedora 13
- Canonical location for known good installer images
Unresolved Questions & Topics
- What do we call the pending release tree?
- When do we branch? Feature Freeze?
- 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
- Do we always make install images for rawhide, or only make images for pending release tree?
- packages going "straight to stable" via bodhi during a freeze
- When and how does signing happen? How will we know if something isn't signed in time to fix it?