From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Closing bugs (?)
Date: Tue, 4 Apr 2000 15:39:17 +0000 [thread overview]
Message-ID: <1000404153917.ZM20523@candle.brasslantern.com> (raw)
In-Reply-To: <200004041433.QAA00831@beta.informatik.hu-berlin.de>
On Apr 4, 4:33pm, Sven Wischnowsky wrote:
} Subject: Closing bugs (?)
}
} Sourceforge supports the `fixed' and `closed' states. Hm, do we want
} to leave it to one of the administrators to actually close a bug or
} should the person who fixed (or tried to fix) it do that?
}
} And why this distinction?
A bug can be closed without being fixed, i.e. "that's not a bug, it's a
feature," or "seeming bug was caused by pilot error," etc.
The way I've typically handled it with GNATS before is that the person
who fixes the bug changes the state to "fixed" ("feedback" in GNATS),
and then it's up to the administrator and/or the person who reported
the bug to agree that it's fixed and change it to "closed".
But maybe we don't need that much supervision, and maybe it's OK to
leave a bug in the "fixed" state forever.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-04 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-04 14:33 Sven Wischnowsky
2000-04-04 15:39 ` Bart Schaefer [this message]
2000-04-04 15:46 ` John Grossi
2000-04-05 8:03 Sven Wischnowsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000404153917.ZM20523@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).