Download as ODP, PPTX
Uploaded byJaroslav Reznik
Fedora planning process - totally new one!
The document outlines the changes made in the planning process for Fedora, introducing two categories for managing changes: self-contained changes and system-wide changes. It highlights the purpose of these changes, improvements in status tracking, and the increased emphasis on inter-team coordination. Additionally, it reflects on the need for feedback and better coordination within the Fedora project while providing resources for further information.
Fedora planning process - totally new one!
- 1. ...totally new one! JaroslavŘezník, Stephen Gallagher Presented by Presentation licensed under Creative Commons CC-BY http://creativecommons.org/licenses/by/3.0/us/ The planning process
- 2. Today's Topics 1. Introduction 2.Whydidwechangethename? 3. Changesinmoredetails 4. Reallifeexample a. What'sinthetemplate 5. Wheredowewanttogonext?
- 3. Who we are ●Jaroslav – The Change Wrangler ● Stephen – Current FESCo member ● And why we are the right people to talk about it ;-)
- 4.
- 5. Changes ● ForFedora19,westartedwithFeatureAnnouncementstothedevel-announcelist – Ithelpedalotbutwewantedmore! ●ForFedora20wemovedfromsimpleFeaturestoChanges,withtwocategories – Self-ContainedChange – System-WideChange
- 6. Why did wechange the name?
- 7. Features ● Featureswereunderstoodmoreas“marketing”ratherthanplanning ● WewantedtomakesureChangesaredifferent –“Shines”tobeusedbymarketingasthelabel
- 8.
- 9. Self-Contained Change ● Changeto isolated package(s), or a general changes with limited scope and impact on the rest of distribution/project ● Examples – Addition of a group of leaf packages ● A new programming language ● A new web framework – A coordinated effort within a SIG with limited impact outside the SIG's functional area ● A new desktop environment that doesn't change existing libraries ● Release of an updated tool kit with constrained uses
- 10. System-Wide Change ● Changesto system-wide defaults ● Critical path components ● Anything that does not meet the definition of “self- contained changes” ● Examples: – Backwards-incompatible library updates – Changes to the installer or boot process
- 11. Status Tracking ● “PercentageComplete” was arbitrary and often inaccurate ● Bugzilla now tracks progress – Developers are familiar with Bugzilla – Used as Tracker bug for dependent pieces – Provides clearer deliverables
- 12. Bugzilla States ● NEW –Change proposal is submitted and announced ● ASSIGNED – Accepted by FESCo with ongoing development ● MODIFIED – change is substantially done and testable – Must be in this state by Alpha Freeze ● ON_QA – Change is code-complete – Ready for testing in the Beta release ● CLOSED as NEXTRELEASE – Change is completed and verified – Will be delivered in next release under development
- 13. Inter-team Coordination ● Planningprocess is the central point to coordinate development ● Provides clear documentation of intent ● Gives other teams an opportunity to comment before Changes land
- 14. What (we think)works ● Announcements – Sometimes leads to flame wars, but people talk to each other! ● Lightened the process for Self-Contained Changes ● Release schedule now based on the submitted Changes
- 15. Bottlenecks – rightcategory? ● Many Change Proposals are on the edge between Self Contained Change and System Wide Change – But we have announcements to sort it out! ● Guidance on categories for “clear” cases – Aka GLIBC should be always System-Wide... ● Sign-offs for coordinated Self-Contained
- 16. Bottlenecks – Changeas idea ● Changes are tied to the next Fedora release – But we want to know what's happening in Fedora X, where X is >> 1000000 too – It's possible (idea as Self Contained Change) but no real process around it! ● Time of announcement ● Is FESCo approval needed?
- 17. Bottlenecks - “Change” ●Too generic name? Change the Change! – But changing name is confusing
- 18. I want toknow more https://fedoraproject.org/wiki/Changes/Policy
- 19.
- 20. Empty Template ● https://fedoraproject.org/wiki/Changes/EmptyTemplate ●Self-Contained Changes and System-Wide Changes follow the same template – Promoting to System-Wide Change is minimally difficult ● Many pieces of the template are optional for Self- Contained Changes
- 21.
- 22. How to makeit better? ● We are looking for feedback ● Several proposals how to change Fedora @Flock – Coordination needed
- 23.
- 24. Questions? Presentation licensed underCreative Commons CC-BY http://creativecommons.org/licenses/by/3.0/us/ Contact: Jaroslav Reznik: jreznik@redhat.com Stephen Gallagher: sgallagh@redhat.com