From Fedora Project Wiki
m (→Updates to 'important' packages: enhance wording to show that enough karma does not mean the update goes directly stable) |
(→Updates to 'important' packages: adjust the style of the rules to the one for all other updates) |
||
| Line 21: | Line 21: | ||
Updates that constitute a part of the 'important' package set (defined | Updates that constitute a part of the 'important' package set (defined | ||
below) must follow the rules as defined for [[Critical_Path_Packages_Proposal|critical path packages]] for | below) '''including security updates''' must follow the rules as defined for [[Critical_Path_Packages_Proposal|critical path packages]] for | ||
pending releases, meaning | pending releases, meaning: | ||
* a [[Proventester]] must portion out one positive [[Bodhi|Bodhi karma]] '''AND''' | |||
* a second logged in tester must portion out one positive [[Bodhi|Bodhi karma]] | |||
The 'important' package set is defined as the following: | The 'important' package set is defined as the following: | ||
Revision as of 20:06, 2 July 2010
This policy is currently being implemented
acceptance tests are not yet live, but the other sections should be now
acceptance tests are not yet live, but the other sections should be now
For a package to be pushed to the stable updates repository, it must meet the following criteria.
Acceptance tests for all updates
This section is not yet enabled in production
All updates, including security updates, must pass acceptance criteria before being pushed.
The list of tests will be:
- Packages must not break dependencies
- Packages must not break upgrade path
- Packages must not introduce new file/package conflicts
- Packages must be able to install cleanly
Additional tests will be set by FESCo with input from QA.
Updates to 'important' packages
Updates that constitute a part of the 'important' package set (defined below) including security updates must follow the rules as defined for critical path packages for pending releases, meaning:
- a Proventester must portion out one positive Bodhi karma AND
- a second logged in tester must portion out one positive Bodhi karma
The 'important' package set is defined as the following:
- The current critical path package set
- All major desktop environments' core functionality (GNOME, KDE, Xfce, LXDE)
- Package updating frameworks (gnome-packagekit, kpackagekit)
- Major desktop productivity apps. An initial list would be firefox, kdebase (konqueror), thunderbird, evolution, kdepim (kmail).
Changes to this criteria would be done by FESCo or their delegate.
All other updates
All other updates must either:
- reach the criteria laid out in section 2 OR
- reach the positive Bodhi karma threshold specified by the updates submitter OR
- spend some minimum amount of time in updates-testing, currently one week
enforcement of one week in updates-testing is not yet enabled in production
Exception process
Any update that wants to bypass these procedures requires majority approval from FESCo.