Changes/Policy

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
m (Fix comment)
(Merge Mitr's proposals)
Line 15: Line 15:
  
 
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is  
 
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is  
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance.   
+
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).   
  
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
Line 61: Line 61:
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
 +
* Feature owners:
 +
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
 +
* Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
 +
* Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 +
 +
* Policies and guidelines: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 +
 +
== Upgrade/compatibility impact ==
 +
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 +
 +
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
N/A
  
 
== How To Test ==
 
== How To Test ==
Line 92: Line 110:
  
 
== Contingency Plan ==
 
== Contingency Plan ==
<!-- If you cannot complete your proposed change by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your change is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
+
* Contingency mechanism: (What to do?  Who will do it?) N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
N/A
+
* Contingency deadline: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 +
* Blocks release? N/A, Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
  
 
== Documentation ==
 
== Documentation ==

Revision as of 15:34, 26 March 2013

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.


Contents

Change Proposal Name

Summary

Owner

  • Name: Your Name
  • Email: <your email address so we can contact you, invite you to meetings, etc.>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Scope

  • Feature owners:
  • Other developers: N/A
  • Release engineering: N/A
  • Policies and guidelines: N/A

Upgrade/compatibility impact

N/A

How To Test

N/A

User Experience

N/A

Dependencies

N/A

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A
  • Contingency deadline: N/A
  • Blocks release? N/A, Yes/No

Documentation

N/A

Release Notes