After reading Bug Triage wiki, I’m still unclear on whether a bug’s final status must be ‘Closed’ with an appropriate Resolution value, or a bug can end in Status = Resolved with a Resolution value.
It would help if some more information be added to the wiki about Resolved v/s Closed status. Thanks.
Closed denotes that no further action will be taken on the bug. Resolved means that a positive outcome has occurred and no further action is needed.
But (if I understand correctly), “Resolved” does not necessarily mean that the fix is available in a Gramps release?
True. Not every resolution involves a code fix.
What I mean is, for a “Resolved” issue that does involve a change to the code, that change may be committed to one (or more?) branches of the code base, but not yet included in the build for a release.
In that case, users who want the fix can either (1) wait for a release that includes it, (2) build their own version from the appropriate branch of the source code, or (3) apply the changes to the their installed copy of the code.
Is that right?
Option 1 is the easiest but sometimes the least satisfying. Option 2 is for users comfortable with building from source. Option 3 is probably not wise but is what I usually end up doing. (I install the packaged release on my Mac and then apply customizations and fixes inside the package.)
Most fixes I will wait for the next release. There are some fixes that I will apply to the current install. I try to stay abreast of the bug list to be aware of what is developing.
Hi @DaveSch thanks for the reply. Let me share Mantis - Issue Lifecycle which says Resolved is one step along the way to an issue being Closed - end state.
Resolving bugs for developers says (emphasis added) “Bugs in maintenance branch projects should not be marked as closed until the developer has committed the change into the corresponding maintenance branch” which implies that resolved bugs should eventually be closed. Currently there are old issues in resolved state in Gramps’ bug tracker. How to tell whether they’re pending a merge per the wiki process?
At the moment the wiki doesn’t talk about Resolved vs Closed states. If every issue ended in Closed state with the appropriate Resolution, data in the bug tracker and queries would be much cleaner.
Thoughts?
The definitions I laid out is how Gramps is using Mantis to track and handle issues.
Once one of the managers/developers changes the status to “Resolved”, it is never then changed to “Closed”. Issue 101 was given the status “Resolved” on 2006-06-05 with the Resolution “Fixed”. There are many bugs with status “Resolved” and the Resolution “No Change Required”
Many of the bugs with the status “Closed” are duplicate bugs. But regardless, Gramps uses “Closed” to denote that no further action will be taken on that particular bug report.
My goal is here is to understand the lifecycle of a bug in Gramps and as I’m reading the wiki I’m trying to fill in gaps so @DaveSch, your knowledge certainly helps thanks. I graphed what’s documented on the wiki, and to incorporate the practice you mentioned that resolved bugs don’t get closed, I put that state in dashed lines.
Could the gramps developers/triage team review this for correctness and completeness? Thanks.
I would remove the “Closed” after Resolved. Even though that would be the workflow from the Mantis wiki, it is not a step used by Gramps. And yes, I see that you have made the link with a broken line.
I do not understand the need for the circle on the far right.
And to be clear, a duplicate bug is not the only scenario where a bug would be listed as closed. A common reason but not the only reason.
“Cannot reproduce”, “not a bug”, and “will not fix” are good reason for closing without other actions.
Hi @DaveSch , the “Closed” state is not based on the Mantis flow, it is documented in Gramps wiki. If this not practiced, we just need to update that in the wiki which is really the confusion which led to this thread:
Resolving bugs for developers says (emphasis added) “Bugs in maintenance branch projects should not be marked as closed until the developer has committed the change into the corresponding maintenance branch” which implies that resolved bugs should eventually be closed.
The start and end state markers have been removed to avoid any confusion. @emyoulation the additional resolutions have been incorporated. I’ll be happy to make an attempt at updating the wiki and include this state diagram if it helps.
Thanks.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
