From Fedora Project Wiki

(Change to numbered list)
(alt.fp.o is now just an alias to dl.fp.o)
 
(15 intermediate revisions by 8 users not shown)
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}}
* At Alpha Milestone, all packages should be testable and feature complete--whether they are "official features" of the release or not
 
* Builds must come from the branch in source control
'''FIXME''': make sure we spell out what is special or different about '''Alpha''' freeze vs. Beta or Final freeze
* Changes to packages at and after the Alpha Milestone must follow the [[Branch Freeze Policy]].
 
* Between Alpha and Beta milestones, daily "Alpha" Live spins can be downloaded at: http://dl.fedoraproject.org/pub/alt/nightly-composes/
* The purpose of the Alpha freeze is to stop changes to ''Critical Path'' packages (need link) so there is adequate time to prepare and test the Alpha release before making it publicly available.
:(These are built continuously from Branched until just before Final 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.
* Between the Alpha and Beta milestones, the official Alpha distribution can be downloaded at: http://fedoraproject.org/get-prerelease
* New packages can still be reviewed, added in CVS and built
* Alpha freeze should not start immediately after mass-rebuild, which could bring broken dependencies. Example could be mass-rebuild in F-15 followed by branching and alpha freeze, which lead to long list of broken dependencies.
 
== 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 [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
 
== Exception Evaluation ==
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.
 
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.  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]]

Latest revision as of 06:00, 2 September 2013

  • At Alpha Milestone, all packages should be testable and feature complete--whether they are "official features" of the release or not
  • Builds must come from the branch in source control
  • Changes to packages at and after the Alpha Milestone must follow the Branch Freeze Policy.
  • Between Alpha and Beta milestones, daily "Alpha" Live spins can be downloaded at: http://dl.fedoraproject.org/pub/alt/nightly-composes/
(These are built continuously from Branched until just before Final release.)
  • Between the Alpha and Beta milestones, the official Alpha distribution can be downloaded at: http://fedoraproject.org/get-prerelease
  • Alpha freeze should not start immediately after mass-rebuild, which could bring broken dependencies. Example could be mass-rebuild in F-15 followed by branching and alpha freeze, which lead to long list of broken dependencies.
Retrieved from "https://fedoraproject.org/w/index.php?title=Alpha_Milestone&oldid=351420"