4,865
edits
Changes
m
→Resolving bugs for developers: Change word to "resolved" as used by Gramps project.
In general, when resolving an issue, it is always a good idea to add a note with the hash of the commit that fixed the problem.
When resolving issues in a maintenance branch, one should always set the "Fixed in version" field to the version of the next release that will be made from that branch. This is done so that the issue properly appears in the ChangeLog Change Log page for that project ( https://gramps-project.org/bugs/changelog_page.php ). Bugs in maintenance branch projects should not be marked as closed until the developer has committed the change into the corresponding maintenance branch. Additionally, it is the developers responsibility to make sure the change has been merged into the master branch.
Bugs in maintenance branch projects should not be marked as resolved until the developer has committed the change into the corresponding maintenance branch. Additionally, it is the developers responsibility to make sure the change has been merged into the master branch.
===MantisBT permissions===