(Linked these in a more Wiki-like style: Only once, first instance) |
(Add info about status of implementation and clarify karma notes.) |
||
| Line 1: | Line 1: | ||
{{admon/important|This policy is currently being implemented| | {{admon/important|This policy is currently being implemented|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 | For a package to be pushed to the stable updates repository, it must | ||
| Line 5: | Line 5: | ||
== Criteria common to all updates == | == Criteria common to all updates == | ||
{{admon/note|This section is not yet enabled in production}} | |||
All updates, including security updates, must pass acceptance criteria before being pushed. | All updates, including security updates, must pass acceptance criteria before being pushed. | ||
| Line 20: | Line 22: | ||
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) must follow the rules as defined for [[Critical_Path_Packages_Proposal|critical path packages]] for | ||
pending releases, meaning that they require positive [[Bodhi|Bodhi karma]] from | pending releases, meaning that they require positive [[Bodhi|Bodhi karma]] from the ProvenTesters group before they go stable. This also includes security updates for | ||
these packages. | these packages. One positive [[Bodhi|Bodhi karma]] for an update in this group must come from a ProvenTester, along with a second [[Bodhi|Bodhi karma]] from any logged in tester. | ||
The 'important' package set is defined as the following: | The 'important' package set is defined as the following: | ||
| Line 38: | Line 40: | ||
* reach the criteria laid out in section 2 '''OR''' | * reach the criteria laid out in section 2 '''OR''' | ||
* reach the positive Bodhi karma threshold specified by the updates submitter '''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 | * spend some minimum amount of time in [[updates-testing]], currently one week | ||
{{admon/note|enforcement of one week in updates-testing is not yet enabled in production}} | |||
= Exception process = | = Exception process = | ||
Revision as of 18:42, 2 July 2010
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.
Criteria common to all updates
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) must follow the rules as defined for critical path packages for pending releases, meaning that they require positive Bodhi karma from the ProvenTesters group before they go stable. This also includes security updates for these packages. One positive Bodhi karma for an update in this group must come from a ProvenTester, along with a second Bodhi karma from any logged in tester.
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
Exception process
Any update that wants to bypass these procedures requires majority approval from FESCo.