From Fedora Project Wiki

No edit summary
Line 6: Line 6:
== Criteria common to all updates ==
== Criteria common to all updates ==


All updates (even security) must pass acceptance criteria before being pushed.
All updates, including security updates, must pass acceptance criteria before being pushed.


The list of tests will be:
The list of tests will be:
Line 15: Line 15:


Additional tests will be set by FESCo with input from QA.
Additional tests will be set by FESCo with input from QA.


== Updates to 'important' packages ==
== Updates to 'important' packages ==
Line 32: Line 31:


Changes to this criteria would be done by FESCo or their delegate.
Changes to this criteria would be done by FESCo or their delegate.


== All other updates ==
== All other updates ==

Revision as of 16:11, 23 March 2010

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. 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.