Changes

Jump to: navigation, search

Bug triage

106 bytes added, 09:30, 22 April 2020
name of program
Help the Gramps project with bug triaging.
The bug/issue tracker for Gramps is located at the following URL: https://www.gramps-project.org/bugs
==Goals of Bug Triage==
Make sure you're using the latest release of Gramps, using the master branch in [[Brief_introduction_to_Git|Git]] is usually best. From a clean install of Gramps attempt to reproduce the bug that is being reported. If you cannot reproduce the bug, post a comment as such - explaining the steps you took to reproduce the bug. If you encounter a different bug, file a new bug report for that problem if one has not been filed already.
* Read a bit of the [httphttps://www.mantisbt.org/documentation.php documentation of mantisbtMantisBT] so you know what is possible.
* Make sure you have Gramps installed so you can test bugs and problems. Create a family tree and import the [[example.gramps ]] file.
It would be beneficial to also run the master branch version of Gramps so as to test bugs that are in the master branch only.
* At the moment only projects Gramps 3.4, Gramps 45.0, Gramps 45.1, and Gramps 4.2 and master are supported, so any bugs not closed or resolved in older versions must be resolved one way or the other:
** resolved in the meantime
** does not apply anymore
** version no longer supported ([httphttps://en.wikipedia.org/wiki/End-of-life_%28product%29 EOL] versions), [[How_to_make_a_backup|backup your family trees]] and install and try with the new version*** See: [[Previous_releases_of_Gramps|Previous releases of Gramps]]
** bug/problem still present, move the bug to the correct project eg it is a feature request
** too little information given, feedback wanted from reporter
{{man note|ALWAYS|be polite when responding to a bug ticket.}}
* For the supported projects, the bugs must be triaged: Duplicate bugs "'''<span style="background:grey">closed</span>'''", set a better bug title so it is more clear for a developer what the bug is about, add extra information. Most important here is to try to duplicate the bug with the [[example.gramps ]] file, as that is what the developer will spend a lot of time trying to do. Fixing a bug always starts with reproducing it, and many times the developer does not succeed in that. Making that possible is the aim of triage. Once a developer sees a bug in front of him, fixing it is often fast.
* Then there is the feature request project. These must be organised somehow. It is best you look at some of those tickets and make a suggestion on how to organize it so that the feature requests remain useful. Also giving better titles is important here, closing duplicates. Don't be afraid to close something saying users must give a better worked out request (but be polite!).
* Those that other people are able to reproduce (or reason about their validity) should be "'''<span style="background:yellow">confirmed</span>'''".
** If a feature request is valid also move it to "'''<span style="background:yellow">confirmed</span>'''". This only confirms it's a possibility and is not a guarantee that the Gramps project will develop and include it in a future release.
* If the bug is blocked waiting for somebody's input, mark it as "'''<span style="background:#e3b7eb">feedback</span>'''".
* If somebody is actively working on a bug, this is best expressed as "'''<span style="background:#c2dfff">assigned</span>'''". If you stop working on a bug, please remove it from '''assigned''' state.
 
===MantisBT permissions===
 
If you don't have MantisBT permissions (the ability to change bugs' status from Unconfirmed to New, Fixed, or Invalid), then feel free to ask on the Gramps-dev List for someone to set the status for you (eg: "Could someone set bug #{{bug|1}} to invalid please?) Once you do this enough, feel free to ask for MantisBT permissions.
==Status==
On ''20152020-0804-2503'', for '''44034733''' reported issues, *'''12841775''' are '''new''', '''feedback''', '''acknowledged''', '''confirmed''' or '''assigned'''; 31.10% <br>(these can be broken down into three two categories the majority of which are '''Feature Request'''s:** Documentation: 6 ( 0.47% )** Feature Requests: 833 ( 64.88% )1090** Gramps(General issues''Open''): 445 ( 34.66% ) )685*'''14674048''' have been '''resolved(fixed)'''; 33.62%*'''1539''' have been '''closed'''; 35.27%
For many years, the ratio [https[File://gramps-projectGramps bug and feature triage.org/bugs/summary_page.php new reports / (fixed and closed) png|left|thumb|1000px|Reported issues], has been increasing at around '''<span style="color:red">+2</span> per day''' ...]
[[File:Bug_triage.png|left|thumb|1000px|Reported issues]]
{{-}}
{{man warn|Note|As the highest created issue number is 8862, sometime in the past 4495 issues disappeared during a mantisdb upgrade, to which a number of existing issues keep referring to.}}
==MantisBT permissions== If you don't have MantisBT permissions {{man warn|Note|As of (2020-04-03) the ability to change bugs' status from Unconfirmed to Newhighest created issue number is 11672, Fixed, or Invalid)sometime in the past 4495 issues disappeared during a mantisdb upgrade, then feel free to ask on the Gramps-dev List for someone which a number of existing issues keep referring to set the status for you (eg: "Could someone set bug #{{bug|1.}} to invalid please?) Once you do this enough, feel free to ask for MantisBT permissions.
[[Category:Developers/Quality Assurance]]
[[Category:Developers/General]]
Retrieved from "https://www.gramps-project.org/wiki/index.php/Special:MobileDiff/59432...76980"

Navigation menu