Alpha Milestone

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (moved Beta Freeze Policy to Alpha Freeze Policy: Beta is now alpha.)
Line 1: Line 1:
 +
{{admon/tip|Ignoring the Freeze Process|Ignoring the freeze process and introducing new packages anyway can result in your package being reverted or reduce the chances of receiving an exception}}.
 +
 
As of the Alpha freeze for a release, no new features or major version bumps are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built).  The purpose of the Alpha freeze is to help ensure that changes have adequate time to be tested as well as to provide some focus on bug-fixing for the release.  Development builds of packages can continue, however they will not be included in the test release unless you request a break of the freeze for your build.
 
As of the Alpha freeze for a release, no new features or major version bumps are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built).  The purpose of the Alpha freeze is to help ensure that changes have adequate time to be tested as well as to provide some focus on bug-fixing for the release.  Development builds of packages can continue, however they will not be included in the test release unless you request a break of the freeze for your build.
  
If you think that you need to break the Alpha freeze, then you should ask for approval.  To do so, file a ticket in our [https://fedorahosted.org/rel-eng/ Trac Space] with the following information: (Note, don't forget to login, or you will not get email notifications of ticket changes)
+
== Requesting an Exception ==
* A description of what you want to change
+
* Rationale for why the change is important enough to be allowed in after the freeze.
+
* Impact of *not* accepting the change at this point of the schedule.
+
* Information on what testing you've already done on the change to help reduce the risk.
+
  
The [[ReleaseEngineering|  release team]]  will evaluate the request and provide feedback.  If the request is rejected, then you'll have to wait for the freeze to end for your package to appear in Rawhide.  Disputes over rejected changes can be escalated to [[PackageMaintainers/MainPageFesco|  FESCo]]  
+
If believe there is a good reason for you to break the Alpha freeze, submit a request for approval to do so by filing a [https://fedorahosted.org/rel-eng/newticket Release Engineering Ticket]. Please include the following information:
 +
* A description of what you want to change
 +
* Rationale for why the change is important enough to be allowed in after the freeze
 +
* Impact of *not* accepting the change at this point of the schedule
 +
* Amount of testing you have performed to mitigate the risk of this change
  
Approval will come in the form of +1's.  Two +1's (without any negative feedback) are necessary to build.  If there is negative feedback, conversation will ensue and a new vote will be issued.
+
== Exception Process ==
 +
The [[ReleaseEngineering| Release Engineering team]]  will evaluate your request and provide feedback. 
 +
* Approval comes in the form of ''+1's'' (meaning ''Yes'' or ''I approve'').   
 +
* Two +1's (without any negative feedback or ''-1's'') are necessary to build.  If there is negative feedback, conversation will ensue and a new vote will be taken.
  
Note that ignoring the freeze process and introducing new features anyway will lead to your package being reverted and a reduction of the chances of an exception being made.
+
If your request is denied, your package will not appear in Rawhide until the freeze ends. If you disagree with Release Engineering's decision you may enter an appeal with [[Fedora_Engineering_Steering_Committee|FESCo]]. To start the appeals process with FESCo [https://fedorahosted.org/fesco/newtplticket create a ticket with FESCo].
  
Once the Alpha freeze has lifted (near the time the Alpha release is made public) changes will be allowed without special request, however we ask that you keep your changes to bugfix in nature and preserve stability of the release as we work toward the final release.
+
Once the Alpha freeze has lifted (near the time the Alpha release is made public) changes will be allowed without special request.  We still ask that you keep your changes to ''bugfix in nature'' to preserve the stability of the release as we work and test towards the final release.
  
 
[[Category:Release Engineering]]
 
[[Category:Release Engineering]]

Revision as of 18:28, 13 January 2010

Idea.png
Ignoring the Freeze Process
Ignoring the freeze process and introducing new packages anyway can result in your package being reverted or reduce the chances of receiving an exception
.

As of the Alpha freeze for a release, no new features or major version bumps are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built). The purpose of the Alpha freeze is to help ensure that changes have adequate time to be tested as well as to provide some focus on bug-fixing for the release. Development builds of packages can continue, however they will not be included in the test release unless you request a break of the freeze for your build.

Requesting an Exception

If believe there is a good reason for you to break the Alpha freeze, submit a request for approval to do so by filing a Release Engineering Ticket. Please include the following information:

  • A description of what you want to change
  • Rationale for why the change is important enough to be allowed in after the freeze
  • Impact of *not* accepting the change at this point of the schedule
  • Amount of testing you have performed to mitigate the risk of this change

Exception Process

The Release Engineering team will evaluate your request and provide feedback.

  • Approval comes in the form of +1's (meaning Yes or I approve).
  • Two +1's (without any negative feedback or -1's) are necessary to build. If there is negative feedback, conversation will ensue and a new vote will be taken.

If your request is denied, your package will not appear in Rawhide until the freeze ends. If you disagree with Release Engineering's decision you may enter an appeal with FESCo. To start the appeals process with FESCo create a ticket with FESCo.

Once the Alpha freeze has lifted (near the time the Alpha release is made public) changes will be allowed without special request. We still ask that you keep your changes to bugfix in nature to preserve the stability of the release as we work and test towards the final release.