From Fedora Project Wiki
Line 69: Line 69:
  
 
== Scope ==
 
== Scope ==
* Proposal owners:
+
* Proposal owners: rearrange the koji tag and target structure, have the testing in place, setup processes to move builds in koji when they pass testing
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
  
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: Pay attention to new notifications and act when necessary
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
  
 
* Release engineering: [https://pagure.io/releng/issue/6621 #6621]  
 
* Release engineering: [https://pagure.io/releng/issue/6621 #6621]  
  
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: This change removes a milestone and all associated deliverables <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: This change removes a milestone and all associated deliverables  
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
 
  
* 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 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: As there is no more Alpha we will need to update the guidelines to have changes be completed for Beta.  We will likely want to add a new checkpoint for change impelemtation that currently needs to be checked at Alpha
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
  
 
* Trademark approval: N/A (not needed for this Change)
 
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
 
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
Line 95: Line 90:
  
 
== User Experience ==
 
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+
Rawhide will be more stable and be suitable for use on a daily basis by all developers and tech enthusiasts.
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
Rawhide will be more stable
 
  
 
== Dependencies ==
 
== Dependencies ==
Line 105: Line 98:
 
releng to make changes to tagging in koji
 
releng to make changes to tagging in koji
 
a tool to move builds from -pending into rawhide when it passes its tests
 
a tool to move builds from -pending into rawhide when it passes its tests
 +
notifications on test failures and delays in getting packages into rawhide
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 111: Line 105:
 
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency deadline: a month before alpha would have occurred  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 
Reinstate Alpha milestone and release. we will know if we are on target a few weeks before when Alpha would have been.
 
Reinstate Alpha milestone and release. we will know if we are on target a few weeks before when Alpha would have been.
  
Line 120: Line 114:
 
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
  
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
[https://www.youtube.com/watch?v=gQskU7P1CKk&t=447s Dennis' Moving everyone to rawhide talk at DevConf]
N/A (not a System Wide Change)
+
[https://www.youtube.com/watch?v=5gqccjyjwFk&t=3s Ralph's Factory 2.0 Talk at DevConf]
  
 
== Release Notes ==
 
== Release Notes ==

Revision as of 01:56, 16 February 2017


No More Alphas

Summary

Fedora will no longer produce Alpha releases.

Owner

Current status

  • Targeted release: Fedora 27
  • Last updated: 2017-02-16
  • 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: rearrange the koji tag and target structure, have the testing in place, setup processes to move builds in koji when they pass testing
  • Other developers: Pay attention to new notifications and act when necessary
  • 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 will likely want to add a new checkpoint for change impelemtation that currently needs to be checked at Alpha
  • 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 and be suitable for use on a daily basis by all developers and tech enthusiasts.

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 notifications on test failures and delays in getting packages into rawhide

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: a month before alpha would have occurred
  • Blocks release? No
  • Blocks product? None

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

Documentation

Dennis' Moving everyone to rawhide talk at DevConf Ralph's Factory 2.0 Talk at DevConf

Release Notes