5,875
edits
Changes
From Gramps
m
→Resolving bugs for developers: mention what hash means
milestone before a previous one is out, '''please manually adjust the target release field before marking the bug resolved,''' otherwise the roadmap display will be inaccurate [http://sourceforge.net/mailarchive/message.php?msg_id=31870821].
In general, when resolving an issue, it is always a good idea to add a note with the hash “commit hash” (also called the Git commit “reference” or “SHA”) of the commit that fixed the problem.
When resolving issues in a maintenance branch, one should always set the "{{man label|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 {{man label|[https://gramps-project.org/bugs/changelog_page.php Change Log]}} page for that project.
