From Fedora Project Wiki
(add template since I lost everything once already :()
 
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- Self Contained or System Wide Change Proposal?
<!-- Self Contained or System Wide Change Proposal?
Use this guide to determine to which category your proposed change belongs to.
Use this guide to determine to which category your proposed change belongs to.
Line 23: Line 21:


<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Change Proposal Name <!-- The name of your change proposal --> =
= No More Alphas <!-- The name of your change proposal --> =


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
Fedora will no longer produce Alpha releases.


== Owner ==
== Owner ==
Line 33: Line 32:
This should link to your home wiki page so we know who you are.  
This should link to your home wiki page so we know who you are.  
-->
-->
* Name: [[User:FASAcountName| Your Name]]
* Name: [[User:Ausil| Dennis Gilmore]],  [[User:Adamwill| Adam Williamson]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <your email address so we can contact you, invite you to meetings, etc.>
* Email: dennis@ausil.us, awilliam@redhat.com
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
Line 46: Line 45:


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/27 | Fedora 27 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 56: 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.


== Benefit to Fedora ==
== 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.
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->


== Scope ==
== Scope ==
* Proposal owners:
* 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
<!-- 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/issues #Releng issue number] (a check of an impact with Release Engeneering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/6621 #6621]  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  include a link to the releng issue.
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->


** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- 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: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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
<!-- 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 ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
There will be no change to existing systems.
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
See that there is no Alpha release any longer
N/A (not a System Wide Change)


== 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 -->
N/A (not a System Wide Change)


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


== 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: N/A (not a System Wide Change) <!-- 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? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== 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. -->


<!-- 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 ==
Line 146: 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 152: 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

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/NoMoreAlpha&oldid=505742"