RPM Upgrade SOP

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(redirect page to new infra-docs)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Description ==
+
{{header|infra}}
<!-- Put a description of the task here.
+
This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/rpmupgrade.txt
-->
+
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.
+
  
 +
For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.
  
== 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]]
 

Latest revision as of 18:08, 19 December 2011

Infrastructure InfrastructureTeamN1.png

This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/rpmupgrade.txt

For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.