From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
## they have passed testing karma checks | ## they have passed testing karma checks | ||
## they have passed autoqa checks | ## they have passed autoqa checks | ||
## | ## if the update is not a bugfix(not including rfes) and the update falls within the critical path or critical path dependencies, then it cannot be included. | ||
## any other requirement fesco decides on. | ## any other requirement fesco decides on. |
Revision as of 18:09, 1 September 2010
updates policy for patch 'tuesdays':
Principle:
Updates should occur at regular intervals by and large. Not everyday and not haphazardly. Security and critical bugfixes should be issued asynchronously, but feature updates, new pkgs and non-critical bugfixes should be issued once a month for the duration of the distros supported lifetime.
specific rules:
- security and critical bugfixes are issued asychronously. FULL STOP.
- if the above require changes/rebuilds to other pkgs then those others pkgs will be included in the async update provided that, if they are an update beyond a rebuild then they have passed a qa check
- all other updates can be included in the monthly update push provided:
- they have passed testing karma checks
- they have passed autoqa checks
- if the update is not a bugfix(not including rfes) and the update falls within the critical path or critical path dependencies, then it cannot be included.
- any other requirement fesco decides on.