From Fedora Project Wiki
(Benefit to Fedora)
m (Contingency Plan)
 
(18 intermediate revisions by 4 users not shown)
Line 55: Line 55:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1432874 #1432874]
  
 
== Detailed Description ==
 
== Detailed Description ==
  
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
By gating Rawhide builds from landing in the compose and gating the publication of composes on automated test results, we will ensure Rawhide will always be at Alpha quality. This gating will make it more generally useful to people as a daily driver and development platform, and means we no longer need to go through the process of building, testing and shipping Alpha releases. The initial testing will be ensuring that a package is can be installed and that it does not break existing package installations. Over time, we can enable extra testing to gate the build going into rawhide.  Builds will land in the buildroot immediately after the build has completed in order to be built against, and before they make it to the compose. We will run the gating testing only to gate builds to the compose and not in order to make the buildroot.
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 ==
 
== Benefit to Fedora ==
  
By keeping rawhide always at Alpha quality or better we provide a compelling environment for people to have the latest and greatest bits. Developers and tech enthusiasts would want to be running rawhide. Which will result in it getting bug fixes quicker and resulting in an overall better development release. We can drop Alpha releases as we will always be at Alpha quality, by no longer doing Alpha we gain an extra 4 weeks in the schedule which will let us do more. We may need to add a Change testing checkpoint to ensure that new Changes are progressing and are testable, without the need of freezing and branching. The cost of the checkpoint milestone will be much less than the current cost of doing an Alpha release is. We will able to branch 4 weeks later in the schedule than we had previously.
+
A Rawhide that is always at least Alpha quality is a more compelling product and may attract more target users (developers) to Fedora. Removing the process overhead of Alpha releases from the cycle frees up release engineering, quality engineering, development and project management resources for other work. It potentially offers more flexibility for the Change development and branching parts of the release cycle. Preventing broken changes from reaching the official Rawhide repository means we are not stuck with fundamentally problematic changes, (bar doing epoch bumps and rebuilds of dependent packages) but can more easily revert them.
  
 
== Scope ==
 
== 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
+
* Proposal owners: rearrange the koji tag and target structure, have the testing in place, setup processes to move builds into koji when they meet gating criteria. The changes would start to be implemented in rawhide shortly after branching Fedora 26
  
 
* Other developers: Pay attention to new notifications and act when necessary
 
* Other developers: Pay attention to new notifications and act when necessary
Line 75: Line 74:
 
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: This change removes a milestone and all associated deliverables  
 
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: This change removes a milestone and all associated deliverables  
  
* 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
+
* Policies and guidelines: As there is no more Alpha, we will need to update the guidelines to indicate changes are to be completed for Beta.  We will likely want to add a new checkpoint for change implementation that was followed for Alpha
  
 
* Trademark approval: N/A (not needed for this Change)
 
* Trademark approval: N/A (not needed for this Change)
Line 100: Line 99:
 
== Contingency Plan ==
 
== Contingency Plan ==
  
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+
 
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency mechanism: Reinstate Alpha milestone and release. We will know if we are on target a few weeks before as when Alpha would have been.
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+
* Contingency deadline: a month before alpha would have occurred (that would have been August 22nd, so, July 22nd is this deadline)
* Contingency deadline: a month before alpha would have occurred   <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks release? No
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
+
* Blocks product? None
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* 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.
 
  
 
== Documentation ==
 
== Documentation ==
 
<!-- 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. -->
  
[https://www.youtube.com/watch?v=gQskU7P1CKk&t=447s Dennis' Moving everyone to rawhide talk at DevConf]
+
* [https://www.youtube.com/watch?v=gQskU7P1CKk&t=447s Dennis' Moving everyone to rawhide talk at DevConf]
[https://www.youtube.com/watch?v=5gqccjyjwFk&t=3s Ralph's Factory 2.0 Talk at DevConf]
+
* [https://www.youtube.com/watch?v=5gqccjyjwFk&t=3s Ralph's Factory 2.0 Talk at DevConf]
  
 
== Release Notes ==
 
== Release Notes ==
Line 122: Line 118:
 
-->
 
-->
  
[[Category:ChangePageIncomplete]]
+
[[Category:ChangeAcceptedF27]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 128: Line 124:
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
  
<!-- Select proper category, default is Self Contained Change -->
+
[[Category:SystemWideChange]]
[[Category:SelfContainedChange]]
 
<!-- [[Category:SystemWideChange]] -->
 

Latest revision as of 02:38, 14 November 2017


No More Alphas

Summary

Fedora will no longer produce Alpha releases.

Owner

Current status

Detailed Description

By gating Rawhide builds from landing in the compose and gating the publication of composes on automated test results, we will ensure Rawhide will always be at Alpha quality. This gating will make it more generally useful to people as a daily driver and development platform, and means we no longer need to go through the process of building, testing and shipping Alpha releases. The initial testing will be ensuring that a package is can be installed and that it does not break existing package installations. Over time, we can enable extra testing to gate the build going into rawhide. Builds will land in the buildroot immediately after the build has completed in order to be built against, and before they make it to the compose. We will run the gating testing only to gate builds to the compose and not in order to make the buildroot.

Benefit to Fedora

A Rawhide that is always at least Alpha quality is a more compelling product and may attract more target users (developers) to Fedora. Removing the process overhead of Alpha releases from the cycle frees up release engineering, quality engineering, development and project management resources for other work. It potentially offers more flexibility for the Change development and branching parts of the release cycle. Preventing broken changes from reaching the official Rawhide repository means we are not stuck with fundamentally problematic changes, (bar doing epoch bumps and rebuilds of dependent packages) but can more easily revert them.

Scope

  • Proposal owners: rearrange the koji tag and target structure, have the testing in place, setup processes to move builds into koji when they meet gating criteria. The changes would start to be implemented in rawhide shortly after branching Fedora 26
  • 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 indicate changes are to be completed for Beta. We will likely want to add a new checkpoint for change implementation that was followed for 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: Reinstate Alpha milestone and release. We will know if we are on target a few weeks before as when Alpha would have been.
  • Contingency deadline: a month before alpha would have occurred (that would have been August 22nd, so, July 22nd is this deadline)
  • Blocks release? No
  • Blocks product? None

Documentation

Release Notes