From Fedora Project Wiki

No edit summary
No edit summary
Line 14: Line 14:
* Packages must be able to install cleanly
* Packages must be able to install cleanly


Additional tests will be set by FESCo with input from QA.
Additional tests will be set by [[FESCO|FESCo]] with input from [[QA|QA]].


== Updates to 'important' packages ==
== Updates to 'important' packages ==


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 for
below) must follow the rules as defined for [[Critical_Path_Packages_Proposal|critical path packages]] for
pending releases, meaning that they require positive karma from a defined group of testers before they go stable. This also includes security updates for
pending releases, meaning that they require positive karma from a defined group of testers before they go stable. This also includes security updates for
these packages.
these packages.
Line 25: Line 25:
The 'important' package set is defined as the following:
The 'important' package set is defined as the following:


* The current critical path package set
* The current [[Critical_Path_Packages|critical path package set]]
* All major desktop environments' core functionality (GNOME, KDE, XFCE, LXDE)
* All major desktop environments' core functionality (GNOME, KDE, XFCE, LXDE)
* Package updating frameworks (gnome-packagekit, kpackagekit)
* Package updating frameworks (gnome-packagekit, kpackagekit)
* Major desktop productivity apps. An initial list would be firefox, kdebase (konqueror), thunderbird, evolution, kdepim (kmail).
* 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.
Changes to this criteria would be done by [[FESCO|FESCo]] or their delegate.


== All other updates ==
== All other updates ==
Line 37: Line 37:


* 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_Guide|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


= Exception process =
= Exception process =


Any update that wants to bypass these procedures would need majority approval from FESCo.
Any update that wants to bypass these procedures would need majority approval from [[FESCO|FESCo]].


[[Category:Package Maintainers]] [[Category:Policy]]
[[Category:Package Maintainers]] [[Category:Policy]]

Revision as of 16:18, 23 March 2010

Important.png
This policy is currently being implemented
Until tooling work is finished, this policy is not live.

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 karma from a defined group of testers before they go stable. This also includes security updates for these packages.

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 would need majority approval from FESCo.