From Fedora Project Wiki
(template!) |
(Problem definition) |
||
| Line 2: | Line 2: | ||
== Overview == | == Overview == | ||
Provide a single, well-known location with information about whether or not Rawhide is ''broken'', and a link to the ''last known-good'' Rawhide tree. | |||
=== Problem Space === | === Problem Space === | ||
Sometimes Rawhide is ''broken''. Brokenness typically comes in one of these types: | |||
* Installer | |||
** Installer images missing | |||
** Installer doesn't work | |||
* Repo | |||
** Metadata is missing | |||
** Package/file conflicts | |||
** Dependency problems | |||
* Functional | |||
** Major bugs with packages in the "Critical Path" (see [[Critical Path Packages Proposal]]) | |||
When Rawhide is broken it's much harder for people to become Rawhide testers, harder for developers to get fixes into the hands of testers, and other such badness. | |||
=== Proposed Solution === | === Proposed Solution === | ||
Revision as of 14:38, 10 June 2009
Overview
Provide a single, well-known location with information about whether or not Rawhide is broken, and a link to the last known-good Rawhide tree.
Problem Space
Sometimes Rawhide is broken. Brokenness typically comes in one of these types:
- Installer
- Installer images missing
- Installer doesn't work
- Repo
- Metadata is missing
- Package/file conflicts
- Dependency problems
- Functional
- Major bugs with packages in the "Critical Path" (see Critical Path Packages Proposal)
When Rawhide is broken it's much harder for people to become Rawhide testers, harder for developers to get fixes into the hands of testers, and other such badness.
Proposed Solution
Scope
Active Ingredients
Component 1
Component 2
Discussion Points
Comments?
To leave a comment, use the Talk page for this proposal.