|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{admon/important|This policy is currently being implemented|acceptance tests are not yet live, but the other sections should be now}}
| | #REDIRECT [[Updates_Policy]] |
| | |
| For a package to be pushed to the stable updates repository, it must
| |
| meet the following criteria.
| |
| | |
| == Acceptance tests for all updates ==
| |
| | |
| {{admon/note|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 'critical path' packages ==
| |
| | |
| Updates that constitute a part of the 'critical path' package set (defined
| |
| below) '''including security updates''' must follow the rules as defined for [[Critical_Path_Packages_Proposal|critical path packages]] for
| |
| pending releases, meaning:
| |
| | |
| * At the time of the request to stable, the update needs to have a [[Bodhi|Bodhi karma]] sum of 2 '''AND'''
| |
| * One of these positive karma points needs to be from a [[Proventester]]
| |
| | |
| | |
| For the purposes of this policy, the 'critical path' package set is defined as the following:
| |
| | |
| * The current [[Critical_Path_Packages|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 definition would be done by FESCo or their delegate.
| |
| | |
| == All other updates ==
| |
| | |
| All other updates must either:
| |
| | |
| * reach the criteria laid out in the previous section '''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.
| |
| | |
| [[Category:Package Maintainers]] [[Category:Policy]]
| |
