RPM Upgrade SOP
From FedoraProject
(Difference between revisions)
(Created page with 'Category:Infrastructure SOPs Category:Release Engineering SOPs') |
|||
| Line 1: | Line 1: | ||
| + | == Description == | ||
| + | <!-- Put a description of the task here. | ||
| + | --> | ||
| + | When upgrading rpm with backwards incompatible changes we need to take a few steps to ensure that we transition smoothly. For both users and the buildsystem. | ||
| + | |||
| + | |||
| + | == Action == | ||
| + | <!-- Describe the action and provide examples | ||
| + | --> | ||
| + | * build the rpm with new features in rawhide (we need to wait 2 (two) weeks before defaulting to new features.) | ||
| + | * build a new rpm with the new features for the buildsystem (we need to test that it wont break anything for older releases). the buildsystem host rpm installs the packages into the chroot. so it needs to be able to handle the new rpms. | ||
| + | * After 2 weeks in rawhide and the buildsystem has been tested and verified to be ok with the change can the changes to rpm macros be triggered. | ||
| + | |||
| + | |||
| + | |||
| + | == Verification == | ||
| + | <!-- Provide a method to verify the action was successful | ||
| + | --> | ||
| + | |||
| + | |||
| + | == Considerations == | ||
| + | <!-- Create a list of things to keep in mind when performing action. | ||
| + | --> | ||
| + | * Should SRPMS be changed? if not try to keep backwards compatibility. | ||
| + | |||
[[Category:Infrastructure SOPs]] | [[Category:Infrastructure SOPs]] | ||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Revision as of 18:46, 12 August 2009
Contents |
Description
When upgrading rpm with backwards incompatible changes we need to take a few steps to ensure that we transition smoothly. For both users and the buildsystem.
Action
- build the rpm with new features in rawhide (we need to wait 2 (two) weeks before defaulting to new features.)
- build a new rpm with the new features for the buildsystem (we need to test that it wont break anything for older releases). the buildsystem host rpm installs the packages into the chroot. so it needs to be able to handle the new rpms.
- After 2 weeks in rawhide and the buildsystem has been tested and verified to be ok with the change can the changes to rpm macros be triggered.
Verification
Considerations
- Should SRPMS be changed? if not try to keep backwards compatibility.
