BugZappers/HouseKeeping

From FedoraProject

< BugZappers(Difference between revisions)
Jump to: navigation, search
(Task Breakdown)
(22 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{autolang|base=yes}}
 +
 
= Fedora Bugzilla Maintenance SOP =
 
= Fedora Bugzilla Maintenance SOP =
This page and the associated pages explain the processes Fedora uses to manage http://bugzilla.redhat.com as it relates to the ''Fedora'' product.  These processes were created based on Fedora's past experiences and anticipated future needs.
+
 
 +
* This page and the associated pages explain the processes Fedora uses to manage http://bugzilla.redhat.com as it relates to the ''Fedora'' product.  These processes were created based on Fedora's past experiences and anticipated future needs.
 +
* See the [[BugZappers/HouseKeeping/Releases | release tracker page]] which contains links to pages for each release where these procedures where run and recorded
  
 
== Task Breakdown ==
 
== Task Breakdown ==
 +
 +
  
 
Tasks to make sure the bug handling policies listed below run smoothly are grouped by when they take place.  These tasks are also included in the comprehensive Fedora release schedule.
 
Tasks to make sure the bug handling policies listed below run smoothly are grouped by when they take place.  These tasks are also included in the comprehensive Fedora release schedule.
Line 14: Line 20:
  
 
== Versioning ==
 
== Versioning ==
 +
 +
 
* Fedora tracks bugs solely based on the version number of the release or ''rawhide''
 
* Fedora tracks bugs solely based on the version number of the release or ''rawhide''
 
** ''rawhide'' always refers the release currently under development which has not been released or reached GA (general availability)
 
** ''rawhide'' always refers the release currently under development which has not been released or reached GA (general availability)
* Fedora does '''not''' create separate ''fedora versions'' in bugzilla  for individual test releases, including, but not limited to: alpha, beta, and preview releases.   
+
* Fedora does '''not''' create separate ''fedora versions'' in bugzilla  for individual test releases, including, but not limited to: alpha and beta releases.   
 
** Fedora tried this structure in the past, but it provided very little benefit and was difficult to maintain and use consistently.
 
** Fedora tried this structure in the past, but it provided very little benefit and was difficult to maintain and use consistently.
 
* The new version number for the next Fedora release is added to Bugzilla on the day of general availability (GA).
 
* The new version number for the next Fedora release is added to Bugzilla on the day of general availability (GA).
Line 22: Line 30:
  
 
== Rawhide Version ==
 
== Rawhide Version ==
* ''Rawhide'' is a unique version number in that it refers to the current release under development.   
+
* ''Rawhide'' is a unique version number in that it refers to the release stream always under development.   
* At or around the final release of a release under development, bugs assigned to the ''rawhide'' version are rebased (changed) to the final release version.
+
* At or around the Feature Freeze milestone, a new release is ''branched'' from ''rawhide.'' 
* '''FIXME''' we need to pick a definitive milestone when this will happen for each release
+
* The branched tree represents the new release of Fedora and a corresponding version number is added to Bugzilla
** For example, after the final release of Fedora 22, all newly reported bugs found in development packages for Fedora 22 are reported against rawhide.  At or around the final release of Fedora 22, all rawhide bugs which are not new features will have their version changed, or ''rebased'' to be "22".
+
** Bugs for the branched release are tracked under the upcoming release number version.
 +
** At ''branching'', bugs assigned to the ''rawhide'' version are rebased (changed) to the new release version as they are most closely associated with that version.
 +
** For example, when Fedora 22 branches from rawhide, all open bugs for ''rawhide'' (with some exceptions) are changed to Fedora ''22.''
 
* Rebasing rawhide bugs each release cycle helps to keep bugs linked with the release (development cycle) they were found in.
 
* Rebasing rawhide bugs each release cycle helps to keep bugs linked with the release (development cycle) they were found in.
 
** Historically this was a problem because ''rawhide'' bugs weren't included in the EOL process and remained open indefinitely.
 
** Historically this was a problem because ''rawhide'' bugs weren't included in the EOL process and remained open indefinitely.
 
** Rebasing ''rawhide'' bugs each release cycle also provides an idea of how many bugs are filed during a given development cycle.
 
** Rebasing ''rawhide'' bugs each release cycle also provides an idea of how many bugs are filed during a given development cycle.
 +
 
=== Rawhide Bugs Excluded From Rebase ===
 
=== Rawhide Bugs Excluded From Rebase ===
 
* Feature requests or ''Requests for Enhancement'' (RFEs)  
 
* Feature requests or ''Requests for Enhancement'' (RFEs)  
Line 34: Line 45:
 
* Package Review requests opened against the ''rawhide'' version are not rebased.
 
* Package Review requests opened against the ''rawhide'' version are not rebased.
 
** Package Review bugs are filed and identified by the ''Package Review'' component
 
** Package Review bugs are filed and identified by the ''Package Review'' component
 +
* Tracking bugs
  
 
== Tracker (Blocker) Bugs ==
 
== Tracker (Blocker) Bugs ==
  
Tracker, sometimes referred to as ''blocker'', bugs are single bugs used to keep track of several other related bugs.  Fedora generally uses tracker bugs to keep track of bugs that need to be fixed during key milestones in the development process.  The BugZappers are responsible for creating the following tracker bugs for each release:
+
Tracker bugs, sometimes referred to as ''blocker'' bugs, are single bugs used to keep track of several other related bugs.  Fedora generally uses tracker bugs to keep track of bugs that need to be fixed during key milestones in the development process ([[QA:SOP_blocker_bug_process|blocker bugs]]) and bugs for which fixes will be accepted through freeze periods ([[QA:SOP_nth_bug_process|nice-to-have bugs]]).  The BugZappers are responsible for creating tracker bugs for each release. See [[BugZappers/HouseKeeping/Trackers| Tracking Bugs]] for a listing of the current tracker bugs and process around creating them.
# Alpha--must be fixed prior to releasing Alpha Release
+
# Beta--must be fixed prior to release Beta Release
+
# Preview--must be fixed prior to release Preview Release
+
# Target--good to fix if possible by GA, but not required
+
# Blocker--must be fixed prior to General Availability (GA)
+
 
+
* Everyone who reports or reviews bugs is reponsible for seeing that applicable bugs are added to the appropriate tracker.  
+
* See [[BugZappers/HouseKeeping/Trackers| Tracking Bugs]] for a listing of the current tracker bugs and process around creating them.
+
 
+
{{Admon/note | ''Tracker'' bugs--commonly referred to as ''blocker'' bugs--are meta-bugs used to monitor a group of bugs that must be resolved before a specific release milestone and are therefore considered to ''block'' the release.}}
+
  
 
== End of Life (EOL) ==
 
== End of Life (EOL) ==
  
* Releases for which updates are no longer provided are considered to be''unmaintained'' and thus ''End of Life'' or commonly referred to as ''EOL''.  Fedora does not track or review bugs for releases where there will be no more updates.
+
* Releases for which updates are no longer provided are considered to be ''unmaintained'' and thus ''End of Life'' or commonly referred to as ''EOL''.   
 +
* Fedora does not track or review bugs for releases where there will be no more updates.
 +
* All bugs for EOL releases are automatically closed on the EOL date after providing a warning in the bug comments, 30 days prior to EOL.
 
* See [[LifeCycle| release life cycle]] for more information about how long releases are maintained and list of releases with their current status.
 
* See [[LifeCycle| release life cycle]] for more information about how long releases are maintained and list of releases with their current status.
  
Line 67: Line 71:
  
 
{{Admon/note | This proposal was circulated for review for a period of three weeks on the Fedora lists and reviewed and approved by FESCo on 2008-03-20}}
 
{{Admon/note | This proposal was circulated for review for a period of three weeks on the Fedora lists and reviewed and approved by FESCo on 2008-03-20}}
 +
 +
----
 +
[[Category:BugTriage]]
 +
[[Category:BugZappers_SOPs]]

Revision as of 08:27, 17 February 2012

Contents

Fedora Bugzilla Maintenance SOP

  • This page and the associated pages explain the processes Fedora uses to manage http://bugzilla.redhat.com as it relates to the Fedora product. These processes were created based on Fedora's past experiences and anticipated future needs.
  • See the release tracker page which contains links to pages for each release where these procedures where run and recorded

Task Breakdown

Tasks to make sure the bug handling policies listed below run smoothly are grouped by when they take place. These tasks are also included in the comprehensive Fedora release schedule.

Versioning

  • Fedora tracks bugs solely based on the version number of the release or rawhide
    • rawhide always refers the release currently under development which has not been released or reached GA (general availability)
  • Fedora does not create separate fedora versions in bugzilla for individual test releases, including, but not limited to: alpha and beta releases.
    • Fedora tried this structure in the past, but it provided very little benefit and was difficult to maintain and use consistently.
  • The new version number for the next Fedora release is added to Bugzilla on the day of general availability (GA).
  • Changes to this policy require review and approval by FESCo.

Rawhide Version

  • Rawhide is a unique version number in that it refers to the release stream always under development.
  • At or around the Feature Freeze milestone, a new release is branched from rawhide.
  • The branched tree represents the new release of Fedora and a corresponding version number is added to Bugzilla
    • Bugs for the branched release are tracked under the upcoming release number version.
    • At branching, bugs assigned to the rawhide version are rebased (changed) to the new release version as they are most closely associated with that version.
    • For example, when Fedora 22 branches from rawhide, all open bugs for rawhide (with some exceptions) are changed to Fedora 22.
  • Rebasing rawhide bugs each release cycle helps to keep bugs linked with the release (development cycle) they were found in.
    • Historically this was a problem because rawhide bugs weren't included in the EOL process and remained open indefinitely.
    • Rebasing rawhide bugs each release cycle also provides an idea of how many bugs are filed during a given development cycle.

Rawhide Bugs Excluded From Rebase

  • Feature requests or Requests for Enhancement (RFEs)
    • Feature requests or RFEs are designated by the FutureFeature keyword
  • Package Review requests opened against the rawhide version are not rebased.
    • Package Review bugs are filed and identified by the Package Review component
  • Tracking bugs

Tracker (Blocker) Bugs

Tracker bugs, sometimes referred to as blocker bugs, are single bugs used to keep track of several other related bugs. Fedora generally uses tracker bugs to keep track of bugs that need to be fixed during key milestones in the development process (blocker bugs) and bugs for which fixes will be accepted through freeze periods (nice-to-have bugs). The BugZappers are responsible for creating tracker bugs for each release. See Tracking Bugs for a listing of the current tracker bugs and process around creating them.

End of Life (EOL)

  • Releases for which updates are no longer provided are considered to be unmaintained and thus End of Life or commonly referred to as EOL.
  • Fedora does not track or review bugs for releases where there will be no more updates.
  • All bugs for EOL releases are automatically closed on the EOL date after providing a warning in the bug comments, 30 days prior to EOL.
  • See release life cycle for more information about how long releases are maintained and list of releases with their current status.
Note.png
An unmaintained release receives no maintenance or updated packages. Therefore bugs are not tracked against these releases. In the future we will seek an enhancement to bugzilla to disable the ability to file bugs against unmaintained versions as there is no value in doing so.

SOP Review & Approval Process

Note.png
This proposal was circulated for review for a period of three weeks on the Fedora lists and reviewed and approved by FESCo on 2008-03-20