Changes/Policy

From FedoraProject

< Changes
Revision as of 10:53, 10 April 2013 by Jreznik (Talk | contribs)

Jump to: navigation, search
Idea.png
Quick Links
If you know the process already, you can jump immediately to an empty feature form.

Contents

Fedora Releases Planning Process

Motivation behind the planning process is to raise the visibility of planned changes, to make coordination and planning effort easier, as otherwise it is nearly impossible to follow all changes happening in such a big project as Fedora is. It has to be easy to submit the Change Proposal, as early as possible, before the change is implemented and even in very early state of idea, to gather community feedback and review.

The list of accepted changes (Change Set) is used by different teams across the project, for example to prepare external facing materials like Release notes and Release announcements.

Planning process is an internal planning and tracking tool and the final release does not have to reflect all proposed changes.

Changes Categories

Fedora Engineering and Steering Committee (FESCo) defined two Change categories:

  1. Self Contained Changes
  2. System Wide Changes

Self Contained Changes

The self contained changes are changes to isolate package(s) or generally all changes with limited scope and impact on the rest of distribution/project. For example addition of a group of leaf packages or coordinated effort within SIG with limited impact outside SIG functional area. Self Contained Changes could be used for early idea state proposals for wider and complex changes.

Public announcement of the new Self Contained Changes helps to co-operate on the change and extends proposed change visibility. Change owners may find help from the community or useful comments. These changes don't have to be thoroughly reviewed by FESCo. Based on the community review, Self Contained Change can be updated to the System Wide Change category and Owner can be asked to provide more details and extend Change Proposal Papge.

Note.png
This will be explained in more details in the link.

The process for Self Contained Features

  • Change Proposal is submitted according to the Change Proposal Submission policy
  • The formal correctness of Proposed Change page is checked by the Wrangler
  • Once the Change Proposal is correct, it's announced on Fedora Devel Announce list by the Wrangler.
  • No documentation process (optional), only release notes advertisement
  • Aggregated list of Change Proposals is added to FESCo agenda no sooner than a week (or more) after the announcement on the mailing list.
    • In case of no complaints (possible breakage/conflicts, coordination needed) on Fedora Devel mailing list/or from FESCo members, FESCo approves those Change Proposals without more scope and etc. investigation. Every team on Fedora devel can share their views and escalate proposed change to FESCo to go through the regular System Wide Changes 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.

Complex System Wide Changes

Complex System Wide Changes are system-wide/defaults or critical path components changing changes which does not belong to Self Contained Changes.

Note.png
This will be explained in more details in the link.

The process

  • Change Proposal is submitted according to the Change Proposal Submission policy
  • The formal correctness of Proposed Change page is checked by the Wrangler
  • Once the Change Proposal is correct, it's announced on Fedora Devel Announce list by the Wrangler.
  • After a week on mailing list FESCo will discuss the change on their meeting.
    • Optionally, the change is assigned to one of the FESCo members/or trusted community member within the functional area, who follows detailed status of the change with FESCo and helps with processes within Fedora (e.g. communicate about high-impact aspects, point out that a buildroot will be neccessary). The shepherd follows on status of the change until final release.
    • 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. At this time FESCo will typically decide whether to activate the contingency plan. Changes for which FESCo can't make this decision one week before beta need to note it on the respective Change wiki page.