From Fedora Project Wiki
(Add critpath link) |
No edit summary |
||
| 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}} | {{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}} | ||
* At Alpha Freeze, all packages should testable and feature complete--whether they are "official features" of the release or not | |||
* Freezing the package collection makes sure there is adequate time to prepare and test the [[Alpha Release]] before making it publicly available. | |||
* | * Changes to [[Critical_Path_Packages|Critical Path Packages]] after Alpha Freeze must follow the exception process described here. | ||
* Changes to non-Critical Path Packages are peer-driven via Bodhi. They do not require an exception from releng, but they should use established the bodhi peer-review, karma system. | |||
* New packages can still be reviewed, added in CVS and built | |||
* 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. | * 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 == | == Requesting an Exception == | ||
If believe there is a good reason for you to break the Alpha freeze, | If believe there is a good reason for you to break the Alpha freeze, build and test your package before submitting 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 | # A description of what you want to change | ||
# Rationale for why the change is important enough to be allowed in after the freeze | # 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 | # 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 | # Amount of testing you have performed to mitigate the risk of this change | ||
{{admon/tip|Exception Ticket Wizzard|As a convience there is a make target called <code>tag-request</code> in your package module that assists in creating a ticket for you}} | |||
== Exception Evaluation == | == Exception Evaluation == | ||
| Line 18: | Line 21: | ||
* Approval comes in the form of ''+1's'' (meaning ''Yes'' or ''I approve''). | * 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. | * 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 accepted, your package will be tagged for inclusion in Rawhide. | |||
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]. | 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]. | ||
Revision as of 01:51, 15 January 2010
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
Ignoring the freeze process and introducing new packages anyway can result in your package being reverted or reduce the chances of receiving an exception
- At Alpha Freeze, all packages should testable and feature complete--whether they are "official features" of the release or not
- Freezing the package collection makes sure there is adequate time to prepare and test the Alpha Release before making it publicly available.
- Changes to Critical Path Packages after Alpha Freeze must follow the exception process described here.
- Changes to non-Critical Path Packages are peer-driven via Bodhi. They do not require an exception from releng, but they should use established the bodhi peer-review, karma system.
- New packages can still be reviewed, added in CVS and built
- 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, build and test your package before submitting 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 Ticket Wizzard
As a convience there is a make target called
As a convience there is a make target called
tag-request in your package module that assists in creating a ticket for youException Evaluation
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 accepted, your package will be tagged for inclusion in Rawhide.
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.