From Fedora Project Wiki
(Dependencies)
Line 102: Line 102:
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
  
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
QA to have tests to detect when a new build breaks dependencies.
N/A (not a System Wide Change)
+
releng to make changes to tagging in koji
 +
a tool to move builds from -pending into rawhide when it passes its tests
  
 
== Contingency Plan ==
 
== Contingency Plan ==

Revision as of 22:06, 7 February 2017


No More Alphas

Summary

Fedora will no longer produce Alpha releases.

Owner

Current status

  • Targeted release: Fedora 27
  • Last updated: 2017-02-07
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

By adding CI and gating on Rawhide we will enable rawhide to be more stable and generally useful to people as a daily driver. As a result rawhide should always be at alpha quality, by keeping Rawhide always at Alpha quality we will be no longer need to do Alpha releases.

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #6621
  • Policies and guidelines: As there is no more Alpha we will need to update the guidelines to have changes be completed for Beta. We may want to add a new checkpoint for basic testability of changes
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

There will be no change to existing systems.

How To Test

See that there is no Alpha release any longer

User Experience

Rawhide will be more stable

Dependencies

QA to have tests to detect when a new build breaks dependencies. releng to make changes to tagging in koji a tool to move builds from -pending into rawhide when it passes its tests

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Reinstate Alpha milestone and release. we will know if we are on target a few weeks before when Alpha would have been.

Documentation

N/A (not a System Wide Change)

Release Notes