User Tools

Site Tools


geda:bug_triage_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
geda:bug_triage_guide [2012/02/20 15:14]
127.0.0.1 external edit
geda:bug_triage_guide [2016/07/25 14:46] (current)
bert Added a link to the pcb bug tracker
Line 1: Line 1:
 +//​Translations of this page are also available in the following languages://​ [[bug_triage_guide.ru|Русский]],​ [[bug_triage_guide.nl|Nederlands]].
 +
 ====== gEDA/gaf and PCB Bug/Feature Request Triage Guide ====== ====== gEDA/gaf and PCB Bug/Feature Request Triage Guide ======
  
-gEDA/​gaf ​uses [[http://​launchpad.net|Launchpad]] for bug and feature request tracking - the gEDA landing page is [[http://​bugs.launchpad.net/​geda | here]].+gEDA/​gaf ​and PCB use [[http://​launchpad.net|Launchpad]] for bug and feature request tracking - the gEDA landing page is [[http://​bugs.launchpad.net/​geda ​| here]] and the PCB landing page is [[http://​bugs.launchpad.net/​pcb ​| here]].
  
 Newly filed bugs and feature requests must be triaged periodically by the developers and others close to the project, in order to progress them smoothly through development and avoid them getting stuck. Newly filed bugs and feature requests must be triaged periodically by the developers and others close to the project, in order to progress them smoothly through development and avoid them getting stuck.
Line 13: Line 15:
     * https://​launchpad.net/​geda/​+bugs?​search=Search&​field.status=New     * https://​launchpad.net/​geda/​+bugs?​search=Search&​field.status=New
     * https://​launchpad.net/​pcb/​+bugs?​search=Search&​field.status=New     * https://​launchpad.net/​pcb/​+bugs?​search=Search&​field.status=New
-  - Grab "git HEAD" of whichever package the bug is in (if you don't have it already) and try to confirm whether the bug is still present or not.+  - Grab "git HEAD" of whichever package the bug is in (if you don't have it already) and try to confirm whether the bug is still present or not. (http://​git.geda-project.org)
   - If the bug is still present, move the status from "​New"​ to "​Confirmed"​   - If the bug is still present, move the status from "​New"​ to "​Confirmed"​
     * If and only if there is a good testcase uploaded that reproduces the bug (or you have created and uploaded one as part of triage), you can move the status to "​Triaged"​     * If and only if there is a good testcase uploaded that reproduces the bug (or you have created and uploaded one as part of triage), you can move the status to "​Triaged"​
     *  //**Note:** it is not good form to mark your own bug "​Confirmed"​.//​     *  //**Note:** it is not good form to mark your own bug "​Confirmed"​.//​
-  - If the bug is absent, make a comment and set the status to one of  +  - If the bug is absent, make a comment and set the status to one of 
-    * "​Invalid," if you are confident that the bug is bogus or misfiled.+    * "​Invalid"​if you are confident that the bug is bogus or misfiled.
       * If the bug is tagged with "​sf-patches"​ shouldn'​t be closed "​Invalid"​. If the patch cannot or will not be accepted, mark it as "​WontFix"​.       * If the bug is tagged with "​sf-patches"​ shouldn'​t be closed "​Invalid"​. If the patch cannot or will not be accepted, mark it as "​WontFix"​.
-    * "Fix Committed," if you believe a fix has been committed in git since the last release; +    * "Fix Committed"​if you believe a fix has been committed in git since the last release; 
-    * "Fix Released," if you believe a fix has been committed that has been in a released version;  +    * "Fix Released"​if you believe a fix has been committed that has been in a released version; 
-    * "​Incomplete," if you ask the reporter a question which needs to be answered to properly assess the bug.+    * "​Incomplete"​if you ask the reporter a question which needs to be answered to properly assess the bug.
   - If the bug affects you personally, hit the link under the title of the bug that lets you state that.   - If the bug affects you personally, hit the link under the title of the bug that lets you state that.
   - If you want to be emailed when the bug is modified, click "​Subscribe"​ on the right hand toolbar.   - If you want to be emailed when the bug is modified, click "​Subscribe"​ on the right hand toolbar.
  
 ===== Triaging Feature Requests ===== ===== Triaging Feature Requests =====
-  ​- Choose a feature request from +//There are two active feature request lists (02-2016)://​ 
-    * https://​launchpad.net/​geda/​+bugs?​search=Search&​field.status=New +  * Launch Pad: 
-    * https://​launchpad.net/​pcb/​+bugs?​search=Search&​field.status=New +     - Choose a feature request from 
-  - If it's not already set, set the Importance to "​Wishlist"​ +       ​* https://​launchpad.net/​geda/​+bugs?​search=Search&​field.status=New 
-  - If you agree with the feature request, select the "Bug affects me" option. This will allow us to track the popularity of a request. +       ​* https://​launchpad.net/​pcb/​+bugs?​search=Search&​field.status=New 
-  - A developer who is sufficiently familiar with the design issues will move the Status from "​New"​ to either "​Confirmed",​ "​WontFix"​ or "​Opinion"​. +     ​- If it's not already set, set the Importance to "​Wishlist"​ 
-  ​+     ​- If you agree with the feature request, select the "Bug affects me" option. This will allow us to track the popularity of a request. 
 +     ​- A developer who is sufficiently familiar with the design issues will move the Status from "​New"​ to either "​Confirmed",​ "​WontFix"​ or "​Opinion"​. 
 +  ​* Geda/PCB Project Wiki: 
 +     - "Wish List" at the bottom of this page: 
 +       * [[http://​wiki.geda-project.org/​pcb:​roadmap]]
geda/bug_triage_guide.1329768895.txt.gz · Last modified: 2012/08/08 13:27 (external edit)