What is the proper way of marking a bug as RESOLVED?
When fixing a bug, always mention the bug number in the commit message and ChangeLog entry. Once the changes are in SVN, paste the relevant part of the ChangeLog entry (or all of it) in the comment field and mark the bug as RESOLVED FIXED. These cross-references help a lot when trying to find when a bug was fixed, its relations to other bugs, and potential regressions. A bug that is fixed in SVN or in an unstable release should be marked as RESOLVED FIXED. Optionally, the reporter or someone other than the one who fixed the bug can mark it as VERIFIED after some testing. When the fix is part of a stable release, it can be marked as CLOSED. This is explained further in A Bug’s Life Cycle except for the difference between stable and unstable releases.
When fixing a bug, always mention the bug number in the commit message. Once the changes are in git, paste the relevant part of the commit message (or all of it) in the comment field and mark the bug as RESOLVED FIXED. These cross-references help a lot when trying to find when a bug was fixed, its relations to other bugs, and potential regressions. A bug that is fixed in git or in an unstable release should be marked as RESOLVED FIXED. Optionally, the reporter or someone other than the one who fixed the bug can mark it as VERIFIED after some testing. When the fix is part of a stable release, it can be marked as CLOSED. This is explained further in A Bug’s Life Cycle except for the difference between stable and unstable releases.
