Alpha Milestone

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Change names to Alpha)
(add recommendation & typo)
(21 intermediate revisions by 7 users not shown)
Line 1: Line 1:
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.
+
* 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
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)
+
* Changes to packages at and after the Alpha Milestone must follow the [[Branch Freeze Policy]].
* A description of what you want to change
+
* Between Alpha and Beta milestones, daily "Alpha" Live spins can be downloaded at: http://alt.fedoraproject.org/pub/alt/nightly-composes/
* Rationale for why the change is important enough to be allowed in after the freeze.
+
:(These are built continuously from Branched until just before Final release.)
* Impact of *not* accepting the change at this point of the schedule.
+
* Between the Alpha and Beta milestones, the official Alpha distribution can be downloaded at: http://fedoraproject.org/get-prerelease
* Information on what testing you've already done on the change to help reduce the risk.
+
* 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.
 
+
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]]
+
 
+
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.
+
 
+
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.
+
 
+
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.
+
  
 
[[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.