Changes, changes and changes
- initial version: 2012-07-25 (mmaslano, mitr, t8m, jreznik)
- latest revision based on feedback from FUDCon Lawrence
Motivation
The aim of this proposal is to lower the barrier to propose changes, to avoid situation where unknown/not proposed changes appears later in the release cycle and leads to conflicts/slip and other issues. But also not to flood FESCo with overwhelming amount of changes and let them concentrate more on important complex changes with system wide impact. The community review is part of proposed process. The "Change process" becomes internal planning tool and will be referred as "Planning process" (even it's difficult to split planning/marketing for truly open and community based project). Selected planning changes will changed as marketing features to create release announcements, talking points etc.
Categories of changes
- "self contained" changes
- "complex changes" with wide impact
Self contained changes
The self contained change could be one very isolated package or change with limited scope, for example adding group of leaf packages or coordinated effort within SIG with limited impact outside SIG functional area. Enhancement of one package without impact on other package is also self contained change.
Public announcement of the new self contained change will help to co-operate on the change and extend proposed change visibility. Change owners can find help or useful comments. Those changes don't have to be thoroughly reviewed by FESCo, which means more time for FESCo on the second category.
Process
- Formal correctness of filled change template will be checked by Change Wrangler and the change will be announced on Fedora Devel Announce list.
- No docs process (optional), only release notes advertisement.
- Aggregated list of changes will be added to FESCo agenda after a week (or more) on mailing list.
- In case of no complaints (possible breakage/conflicts, coordination needed) on Fedora Devel mailing list/or from FESCo members, FESCo will approve those changes without more investigation about the scope etc. Every team on Fedora devel can share their views and escalate change to FESCo to go through the regular Change process. Change owner could be asked to provide more details/or move the change to the "complex changes" category. FESCo members are encouraged to ask questions on the mailing list instead of waiting for the meeting.
Scheduling
- Self contained changes follows the same schedule for the Change Submission deadline as complex changes (to reasonably bump them into the "complex" category).
Complex changes with system-wide impact
This changes are system-wide/defaults changing changes or critical path components. They can impact hundreds of packages (upgrade of gcc, glibc, change default from python2 -> python3, UsrMove, etc.). FESCo must have more time to review those changes, help change maintainer with defining the scope or help with contacting other impacted teams.
Process
- Formal correctness of filled change template will be checked by Change Wrangler and the change will be announced on Fedora Devel Announce list.
- After a week on mailing list FESCo will discuss the change on their meeting.
- Optionally, the change could be assigned to one of FESCo members/or trusted community member within the functional area, who will follow detailed status of the change with FESCo and help with process in Fedora (e.g. communicate about high-impact aspects, point out that a buildroot will be neccessary). The shepherd will follow on status of the change until release of Fedora. (We should be able to track the real status, better than with 80% which magically grow to 100% during Beta freeze.
- Fedora QA reviews announced changes on Devel Announce list to commit to testing of the change and/or adjust release criteria in case of need.
- Status of complex changes will be re-reviewed by FESCo one week before Beta Freeze.
Scheduling
- Change Freeze as a hard deadline for complex changes, to allow integration and possible mass rebuilds etc.
What must be defined or added into current system:
Define Scope sections more clearly:
- release engineering impact - ticket to rel-engs, to understand impact of proposed change
- Needs a mass rebuild? (To be considered for scheduling, to schedule mass rebuilds for more changes together etc.)
- List of specific actions for contingency plan (remember rewrite of anaconda!)
- Whether the change is release blocking or not could be decided during review of the change. Blocker could be anaconda, but not changes which can use contingency plan.
New Change Template:
All sections of this template are required for review by FESCo or only for Changes to be approved by FESCo?
Required fields: Summary, Owner, Current Status, Scope (list of dependencies), ...
- Who's actually responsible for work on broken things related to the new change?
- Change templates - must be all field filled even for self-contained changes?
- Talk page should be used only for discussion about the proposed page before announcement - direct technical dicusssion to mailing lists
F(n+1) planning process:
- By the time Fn branches, open planning process for F(n+1)
- to allow planning of large-scale changes earlier
- has to be communicated on the branch day
Planning process
The idea is to split internal planning and tracking process for change and marketing process.
- "Change process" is being renamed to "Planning process"
- Marketing/docs teams to prepare list of "Changes" communicated to users/press
To do
- We would like rawhide "merge windows": prepare your large change in branches / side tags, and have a complete integration into rawhide finished in <= 1 week. (Need to prepare howtos/guides.)