No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
[http://techbase.kde.org/File:DarioAndres_GuideToBugTriaging_Workflow.png] | [[File:http://techbase.kde.org/File:DarioAndres_GuideToBugTriaging_Workflow.png]] | ||
= How to triage KDE in Fedora = | = How to triage KDE in Fedora = | ||
Revision as of 13:36, 13 April 2010
This is a work in progress. Comments to tuxbrewr /at/ fedoraproject.org.
File:Http://techbase.kde.org/File:DarioAndres GuideToBugTriaging Workflow.png
How to triage KDE in Fedora
1. Identify the component(s) you wish to triage and request the WATCHBUGZILLA ACL in the Fedora Package Database. This will insure you are CC'd on any new bugs submitted against that component.
2. You can then create a search in the RedHat Bugzilla for bugs filed against component you are interested in. You will need to specify the following to only include bugs which have not been triaged. Status must be NEW and the keyword Triaged should not have been set.
3. Check for duplicates. Open 2 additional tabs in your browser of choice, with 1 tab containing bugzilla.redhat.com and the other bugs.kde.org. This will allow you to search for duplicates while keeping the original report available. If you find a duplicate in the redhat bugzilla you can close the new report as a duplicate of the existing report. If there is existing report in the redhat bugzilla then you can check the kde bug system to see if the issue has already been reported upstream. If it has then note the upstream bug # in the redhat report and close it as UPSTREAM. If not upstream report exists then continue to step 4.
4.