fedora planning process - totally new one!
TRANSCRIPT
...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
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?
Who we are
● Jaroslav– The Change Wrangler
● Stephen– Current FESCo member
● And why we are the right people to talk about it ;-)
Introduction
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
Why did we change the name?
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
Changes in more details
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
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
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
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
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
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
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
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?
Bottlenecks - “Change”
● Too generic name? Change the Change!– But changing name is confusing
I want to know more
https://fedoraproject.org/wiki/Changes/Policy
Real life examples
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
Next steps?
How to make it better?
● We are looking for feedback● Several proposals how to change Fedora @Flock
– Coordination needed
We have a new planning process
We want better coordination within the Project
Two Change categories
Summary
Questions?
Presentation licensed under Creative Commons CC-BYhttp://creativecommons.org/licenses/by/3.0/us/
Contact:Jaroslav Reznik: [email protected] Gallagher: [email protected]