From Fedora Project Wiki
(Created page with '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 ...') |
No edit summary |
||
Line 1: | Line 1: | ||
updates policy for patch 'tuesdays': | updates policy for patch 'tuesdays': | ||
Principle: | '''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: | |||
'''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 | |||
## <something here about the amount of churn and impacted examples> | |||
## any other requirement fesco decides on. |
Revision as of 17:41, 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
- <something here about the amount of churn and impacted examples>
- any other requirement fesco decides on.