Fedora 18 Virtualization Administration Guide - Fedora Documentation
Fedora planning process - totally new one!
-
Upload
jaroslav-reznik -
Category
Technology
-
view
103 -
download
0
Transcript of Fedora planning process - totally new one!
![Page 1: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/1.jpg)
...totally new one!
Jaroslav Řezník, Stephen Gallagher
Presented by
Presentation licensed under Creative Commons CC-BYhttp://creativecommons.org/licenses/by/3.0/us/
The planning process
![Page 2: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/2.jpg)
Today's Topics1. Introduction
2. Why did we change the name?
3. Changes in more details
4. Real life example
a. What's in the template
5. Where do we want to go next?
![Page 3: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/3.jpg)
Who we are
● Jaroslav– The Change Wrangler
● Stephen– Current FESCo member
● And why we are the right people to talk about it ;-)
![Page 4: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/4.jpg)
Introduction
![Page 5: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/5.jpg)
Changes● For Fedora 19, we started with Feature Announcements to the devel-announce list
– It helped a lot but we wanted more!● For Fedora 20 we moved from simple Features to Changes, with two categories
– Self-Contained Change
– System-Wide Change
![Page 6: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/6.jpg)
Why did we change the name?
![Page 7: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/7.jpg)
Features● Features were understood more as “marketing” rather than planning
● We wanted to make sure Changes are different
– “Shines” to be used by marketing as the label
![Page 8: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/8.jpg)
Changes in more details
![Page 9: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/9.jpg)
Self-Contained Change
● Change to 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
![Page 10: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/10.jpg)
System-Wide Change
● Changes to 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
![Page 11: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/11.jpg)
Status Tracking
● “Percentage Complete” was arbitrary and often inaccurate
● Bugzilla now tracks progress– Developers are familiar with Bugzilla
– Used as Tracker bug for dependent pieces
– Provides clearer deliverables
![Page 12: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/12.jpg)
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
![Page 13: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/13.jpg)
Inter-team Coordination
● Planning process is the central point to coordinate development
● Provides clear documentation of intent● Gives other teams an opportunity to comment before
Changes land
![Page 14: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/14.jpg)
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
![Page 15: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/15.jpg)
Bottlenecks – right category?
● 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
![Page 16: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/16.jpg)
Bottlenecks – Change as 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?
![Page 17: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/17.jpg)
Bottlenecks - “Change”
● Too generic name? Change the Change!– But changing name is confusing
![Page 18: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/18.jpg)
I want to know more
https://fedoraproject.org/wiki/Changes/Policy
![Page 19: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/19.jpg)
Real life examples
![Page 20: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/20.jpg)
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
![Page 21: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/21.jpg)
Next steps?
![Page 22: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/22.jpg)
How to make it better?
● We are looking for feedback● Several proposals how to change Fedora @Flock
– Coordination needed
![Page 23: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/23.jpg)
We have a new planning process
We want better coordination within the Project
Two Change categories
Summary
![Page 24: Fedora planning process - totally new one!](https://reader031.fdocuments.in/reader031/viewer/2022032714/55aa3a321a28ab212a8b461b/html5/thumbnails/24.jpg)
Questions?
Presentation licensed under Creative Commons CC-BYhttp://creativecommons.org/licenses/by/3.0/us/
Contact:Jaroslav Reznik: [email protected] Gallagher: [email protected]