[chirp_devel] Marking Issues
When an issue is complete, should it be marked "resolved" or "closed" or is one as good as the other.
Thanks, Jim KC9HI
When an issue is complete, should it be marked "resolved" or "closed" or is one as good as the other.
Eventually, it needs to be closed. That's what makes it go away and not show up as an active thing. It can still be searched, but not normally displayed in lists.
Historically I think we've used the resolved state for things like "I've fixed this and sent the patch, waiting for a build" or something. That level of detail is really not necessary, but fine if you want to do it. However, everything should be closed once it's merged/released/etc.
--Dan
Thanks Dan.
Jim
On Mon, Jun 22, 2015 at 10:22 AM, Dan Smith dsmith@danplanet.com wrote:
When an issue is complete, should it be marked "resolved" or "closed" or is one as good as the other.
Eventually, it needs to be closed. That's what makes it go away and not show up as an active thing. It can still be searched, but not normally displayed in lists.
Historically I think we've used the resolved state for things like "I've fixed this and sent the patch, waiting for a build" or something. That level of detail is really not necessary, but fine if you want to do it. However, everything should be closed once it's merged/released/etc.
--Dan
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (2)
-
Dan Smith -
Jim Unroe