From Fedora Project Wiki
m
 
Line 32: Line 32:
 
* People representing Fedora Working Groups and [https://fedoraproject.org/wiki/Category:SIGs?rd=SIGs Special Interest Groups, present on the meeting]
 
* People representing Fedora Working Groups and [https://fedoraproject.org/wiki/Category:SIGs?rd=SIGs Special Interest Groups, present on the meeting]
  
The team of evaluators meets on regular bi-weekly meetings on Wednesday at 14:00 UTC on [https://apps.fedoraproject.org/calendar/location/fedora-meeting%40irc.freenode.net/ fedora-meeting@irc.freenode.net channel]. (Right after the Fedora Council meeting; like that meeting, this will change with Daylight Saving Time.) Purpose of the regular meeting is to review bugs nominated to the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] and set the priority of these bugs, or denominate bugs not approved for the list. It is required to have a quorum on the meeting (at least three members of the team needs to be present). Members of the Evaluation team can also vote in advance in the bug if they can not attend the meeting.
+
The team of evaluators meets on regular bi-weekly meetings on Wednesday at 15:00 UTC on [https://apps.fedoraproject.org/calendar/location/fedora-meeting%40irc.freenode.net/ fedora-meeting@irc.freenode.net channel]. (Right after the Fedora Council meeting; like that meeting, this will change with Daylight Saving Time.) Purpose of the regular meeting is to review bugs nominated to the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] and set the priority of these bugs, or denominate bugs not approved for the list. It is required to have a quorum on the meeting (at least three members of the team needs to be present). Members of the Evaluation team can also vote in advance in the bug if they can not attend the meeting.
  
 
All the bugs reviewed during the Evaluation meeting are marked by setting ''"Triaged"'' keyword in the bug. If a bug is approved as an ''"Prioritized bug"'' it needs to have sets its priority. The priority of an approved bug, agreed on the Evaluation meeting, is written, in ''"PM Score"'' field of the bug. Priority is expressed by a number from 1 to 10, where 1 means the highest priority and 10 the lowest one. After the evaluation meeting, the chairman exports the list of all Prioritized bugs to the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] and sends a report to the [triage@lists.fedoraproject.org Triage] mailing list. The date when a bug was evaluated for the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] is recorded in the ''"PgM Internal"'' field of the bug (this is then used for the Ageing).
 
All the bugs reviewed during the Evaluation meeting are marked by setting ''"Triaged"'' keyword in the bug. If a bug is approved as an ''"Prioritized bug"'' it needs to have sets its priority. The priority of an approved bug, agreed on the Evaluation meeting, is written, in ''"PM Score"'' field of the bug. Priority is expressed by a number from 1 to 10, where 1 means the highest priority and 10 the lowest one. After the evaluation meeting, the chairman exports the list of all Prioritized bugs to the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] and sends a report to the [triage@lists.fedoraproject.org Triage] mailing list. The date when a bug was evaluated for the [[Fedora_Program_Management/Prioritized_bugs_and_issues|"Prioritized bugs and issues" list]] is recorded in the ''"PgM Internal"'' field of the bug (this is then used for the Ageing).

Latest revision as of 16:01, 28 August 2018


The Fedora Prioritized bugs and issues process

The purpose of this process is to help with processing backlog of bugs and issues found during the development, verification and use of Fedora distribution. The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues. The general criterion for such bugs is "Failure to resolve this bug will result in unpleasantness for a subjectively large subset of users".

The process description

All the bugs and issues on Fedora distribution are tracked in Bugzilla. As such, every item on the "Prioritized bugs and issues" list has assigned a bug ID and can be tracked using standard Bugzilla tools.

The process consist of three main parts:

  • Nomination
  • Evaluation
  • Ageing

Nomination

Issues eligible for this status would be those which do not necessarily fail a release criterion but which have critical impact on a Fedora Edition or on a council-approved Fedora Objective. Issues may also be nominated from the Common Bugs list when they are deemed by QA to have critical impact.

Anyone from the Fedora community (having at least cla_done in FAS) can nominate a bug to be evaluated for inclusion to the "Prioritized bugs and issues" list. The nomination is done by writing PrioritizedBug keyword into Whiteboard field of the tracking bug. (if you are unsure how to do this, you can contact a member of the Evaluation team and ask for a help).

The list of currently nominated bugs, waiting for evaluation, can be seen using the Bugzilla search tool with the following conditions:

  • Keywords: (contains none of the words) Triaged
  • Whiteboard: (contains all of the words) PrioritizedBug

Or you can simply follow this link to search for bugs nominated for evaluation: Nominated Prioritized bugs and issues

Evaluation

Evaluation of nominated bugs is done by the Evaluation team. This team is comprised of FPL, FPgm and people representing Fedora Working Groups and Special Interest Groups. The team does not have fixed group of members. Instead members of the Evaluation team are formed at the beginning of the meeting during Roll Call.

The team of evaluators meets on regular bi-weekly meetings on Wednesday at 15:00 UTC on fedora-meeting@irc.freenode.net channel. (Right after the Fedora Council meeting; like that meeting, this will change with Daylight Saving Time.) Purpose of the regular meeting is to review bugs nominated to the "Prioritized bugs and issues" list and set the priority of these bugs, or denominate bugs not approved for the list. It is required to have a quorum on the meeting (at least three members of the team needs to be present). Members of the Evaluation team can also vote in advance in the bug if they can not attend the meeting.

All the bugs reviewed during the Evaluation meeting are marked by setting "Triaged" keyword in the bug. If a bug is approved as an "Prioritized bug" it needs to have sets its priority. The priority of an approved bug, agreed on the Evaluation meeting, is written, in "PM Score" field of the bug. Priority is expressed by a number from 1 to 10, where 1 means the highest priority and 10 the lowest one. After the evaluation meeting, the chairman exports the list of all Prioritized bugs to the "Prioritized bugs and issues" list and sends a report to the [triage@lists.fedoraproject.org Triage] mailing list. The date when a bug was evaluated for the "Prioritized bugs and issues" list is recorded in the "PgM Internal" field of the bug (this is then used for the Ageing).

The list of currently approved bugs, can be seen using the Bugzilla search tool with the following conditions:

  • Keywords: (contains all of the words) Triaged
  • Whiteboard: (contains all of the words) PrioritizedBug

Or you can simply follow this link to search for bugs nominated for evaluation: Approved Prioritized bugs and issues

Ageing

After every major release of Fedora distribution all the not resolved "Prioritized bugs and issues" which were approved for the list more then 6 months before the release date are re-evaluated on a "Big evaluation meeting". The "Big evaluation meeting" is an extended regular "Evaluation meeting" where members of the Evaluation team are reviewing these old bugs for their priority. This should ensure housekeeping of the "Prioritized bugs and issues" list and avoid choking of the "Prioritized bugs and issues" list by obsolete bugs or issues.