Fedora 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 milestone freeze periods ( freeze exception bugs). Tracker bugs are single bugs used to keep track of several other related bugs. Package Review bugs are filed and identified by the Package Review component.Package Review requests opened against the rawhide version are not rebased.Feature requests or RFEs are designated by the FutureFeature keyword.Feature requests or Requests for Enhancement (RFEs).Rebasing rawhide bugs each release cycle also provides an idea of how many bugs are filed during a given development cycle.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 helps to keep bugs linked with the release (development cycle) they were found in.For example, when Fedora 22 branches from rawhide, all open bugs for rawhide (with some exceptions) are changed to Fedora 22.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.Bugs for the branched release are tracked under the upcoming release number version.The branched tree represents the new release of Fedora and a corresponding version number is added to Bugzilla.At or around the Feature Freeze milestone, a new release is branched from rawhide.Rawhide is a unique version number in that it refers to the release stream always under development.Changes to this policy require review and approval by FESCo.Each release is added to Bugzilla at the point it is branched from Rawhide.Fedora tried this structure in the past, but it provided very little benefit and was difficult to maintain and use consistently.Fedora does not create separate versions in Bugzilla for pre-release milestones (e.g.Fedora tracks bugs solely for numbered releases or Rawhide.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. See the release tracker page which contains links to pages for each release where these procedures where run and recorded.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 as it relates to the Fedora product.1.3.1 Rawhide Bugs Excluded From Rebase.

Fedora bugzilla