Alpha Milestone

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Use bold)
(add recommendation & typo)
(7 intermediate revisions by 6 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
* At Alpha Freeze, all packages should testable and feature complete--whether they are "official features" of the release or not
+
* Changes to packages at and after the Alpha Milestone must follow the [[Branch Freeze Policy]].
* Freezing the package collection makes sure there is adequate time to prepare and test the [[Alpha Release]] before making it publicly available.
+
* Between Alpha and Beta milestones, daily "Alpha" Live spins can be downloaded at: http://alt.fedoraproject.org/pub/alt/nightly-composes/
* Changes to [[Critical_Path_Packages|Critical Path Packages]] after Alpha Freeze must follow the exception process described here.
+
:(These are built continuously from Branched until just before Final release.)
* Changes to non-Critical Path Packages are peer-driven via [https://admin.fedoraproject.org/updates Bodhi]. They do not require an exception from Release Engineering, but they should use established the Bodhi peer-review, karma system.
+
* 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.
* 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 ==
+
{{admon/note|Build and Test First| 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 request a freeze break, 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
+
# The koji build nvr (name-version-release)
+
# 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
+
 
+
{{admon/tip|Exception Ticket Wizard|As a convenience there is a <code>make</code> target called <code>tag-request</code> in your package module that assists in creating a ticket for you.}}
+
 
+
== 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 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]. 
+
 
+
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 13:50, 25 February 2011

  • 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://alt.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.