296
edits
Changes
→3. Submit new bug: this pearl must be preserved for posterity. Would you submit a bug with "forgot what happened" being the only meaningful info in it?!
{{languages|How to report bugs}}The bug/issue tracker for GRAMPS Gramps is located at the following URL: http://bugs.gramps-project.org
This bug/issue tracker allows users and developers to log new issues and track them as they progress. Please take some time to read the issue tracker instructions below and read '''[[How to create a good bug report|how to create a good bug report]]'''. Also, have a look at '''[[Known_issues|known issues]]''' and '''[[Common_problems|common problems]]'''.
==Report a bug==
===1. Login===
To report a bug, you must have a login account on http://bugs.gramps-project.org, which is the GRAMPS Gramps bug tracker. When you create a user account, remember that it can take up to 12 hours before a notification email is send to you. Only after clicking on the link in the email can you submit bugs. Your email address will be handled confidentially.
===2. Search existing bugs===
===3. Submit new bug===
Click on Report Issue, and enter the required information, see below on how to select the project to which the bug belongs. Be verbose, the developers are bad at mind reading. We shall mercilessly close the bugs which have no meaningful information at all, such as #{{bug|7126}}. Do not forget to list the GRAMPS Gramps version you are using. You can check this in GRAMPS Gramps by clicking in the GRAMPS Gramps program the Help menu, option About.
==== Projects ====
#The '''Feature Requests''' project is a place for recording requests for new features.
#The projects with names that look like '''Gramps x.x.X''' are where issues are reported that apply specifically to a maintenance branch (see [http://www.gramps-project.org/wiki/index.php?title=[Brief_introduction_to_SVN#Types_of_branches |Types of Branches]]). A separate project exists for each maintenance branch.#The '''Gramps Trunk''' project should only be used by developers and testers of the latest code. It is a place for recording issues that only apply to the trunk in Subversion (see [http://www.gramps-project.org/wiki/index.php?title=[Brief_introduction_to_SVN#Types_of_branches |Types of Branches]]). There is only one "Gramps Trunk" project because there is only one trunk in the Subversion repository
==== How to proceed ====
The first step in submitting an issue on the tracker is to determine which project it belongs to.
*If the issue represents functionality that does not currently exist in GRAMPSGramps, then the issue should be filed under the '''Feature Requests''' project.
*If the issue represents a problem with functionality that has been released in a stable release of code, then the issue should be filed under the project that corresponds to the maintenance branch for that release. For example, a bug found in GRAMPS Gramps 3.2.6 should be filed under the '''Gramps 3.2.X''' project.
*If the issue represents a problem with functionality that only exists in trunk, or the problem exists in trunk, but not any stable releases, then the issue should be filed under the '''Gramps Trunk''' project.
==Bug triage==
Help the GRAMPS Gramps project [[Bug triage]].
==Syntax==
[[Category:Developers/General]]
[[Category:Developers/Quality Assurance]]
