On Wed, 25 Oct 2006 14:44:02 +0200, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> On 10/25/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: >> When should a bug be closed? I have resolved some bugs but I haven't set >> them to closed, but only to resolved, even though the testcases I've run >> hints that they are fixed. I had an idea that another dev should verify >> that the bug really is fixed. Is this feasible? > > If it was me who submitted the bug, or the bug fix is trivial enough, > I simply set it to status:closed + resolution:fixed. If the bug was > submitted by someone else and/or is a tricky one, I set it to resolved > and wait until the submitter (or someone else) verifies that the > proposed fix works before closing it. > > Seems to be a reasonable process, I think. > Yes, but one danger is that those tricky bugs are left hanging if noone verifies them. -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
