[gobolinux-devel] Closing bugs

[Hisham Muhammad]

On 10/25/06, Jonas Karlsson <jonka750 at student.liu.se> wrote:
> On Wed, 25 Oct 2006 14:44:02 +0200, Lucas C. Villa Real
> <lucasvr at gobolinux.org> wrote:
>
> > On 10/25/06, Jonas Karlsson <jonka750 at student.liu.se> 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.

Yeah, I think we all still need to figure out how to deal with this.
Requiring someone else to verify it every time sounds a bit too
bureaucratic to me, but it seems to make sense on some cases. I marked
bugs as "fixed" but left as "open", for example, when it was a package
problem in the ISO that I fixed but it had not been committed into the
ISO repository (to make sure the fix would not be missed). For quick
fixes on scripts that look obviously right, I think fixing and closing
is fine. When I'm not sure about it, I leave it open and ask for
feedback (either on-list or directly to whoever I think will be able
to solve my doubts). I don't know, that's how I've been doing it so
far, don't know if it's the best way to proceed.

-- Hisham