Kevin Zheng
11 years ago
Hi there,
The Crossfire bug/patch tracker on SourceForge uses states to keep track
of the state of a bug report/patch. In order to make it more useful, I
propose removing several states and adding new ones to clear things up.
The first state should still be "open", meaning that it was just
submitted, is unread, and very likely needs feedback from the sender.
This means we can remove "unread".
Next, there should be "analyzed". The problem is understood and a
solution is being sought.
Next, "feedback". Further work requires additional information from the
originator or the community?possibly confirmation of the effectiveness
of a proposed solution.
Next, "patched". A patch has been committed, but some issues (e.g.
confirmation from originator) are still open.
Next, "suspended". The problem is not being worked on, due to lack of
information or resources. This is a prime candidate for somebody who is
looking for a project to do. If the problem cannot be solved at all, it
will be closed, rather than suspended. This should replace
"pending-wont-fix".
Finally, some of the closed states are ambiguous and should be removed.
"closed-postponed", "closed-remind", and "closed-accepted" are prime
candidates because they are redundant. "cloed-wont-fix" is the same as
invalid, so remove that too.
These changes should apply to both the bug and patch tracker, and
probably the feature request tracker as well.
Thanks,
Kevin Zheng
The Crossfire bug/patch tracker on SourceForge uses states to keep track
of the state of a bug report/patch. In order to make it more useful, I
propose removing several states and adding new ones to clear things up.
The first state should still be "open", meaning that it was just
submitted, is unread, and very likely needs feedback from the sender.
This means we can remove "unread".
Next, there should be "analyzed". The problem is understood and a
solution is being sought.
Next, "feedback". Further work requires additional information from the
originator or the community?possibly confirmation of the effectiveness
of a proposed solution.
Next, "patched". A patch has been committed, but some issues (e.g.
confirmation from originator) are still open.
Next, "suspended". The problem is not being worked on, due to lack of
information or resources. This is a prime candidate for somebody who is
looking for a project to do. If the problem cannot be solved at all, it
will be closed, rather than suspended. This should replace
"pending-wont-fix".
Finally, some of the closed states are ambiguous and should be removed.
"closed-postponed", "closed-remind", and "closed-accepted" are prime
candidates because they are redundant. "cloed-wont-fix" is the same as
invalid, so remove that too.
These changes should apply to both the bug and patch tracker, and
probably the feature request tracker as well.
Thanks,
Kevin Zheng