From: "John Grossi" <jgrossi@bbnplanet.com>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: Closing bugs (?)
Date: Tue, 4 Apr 2000 11:46:12 -0400 [thread overview]
Message-ID: <NBBBLHNFOKNOPEBNMKGFGEAPEBAA.jgrossi@bbnplanet.com> (raw)
In-Reply-To: <1000404153917.ZM20523@candle.brasslantern.com>
> 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?
Speaking as a QA person, there is a large distinction between closed and
fixed states.
A "fixed bug" is one that the developer has entered code that he believes
fixes the problem.
A closed bug is one that's been built, and successfully survives a unit test
and system test.
Lots of code crosses my desk that is "fixed" and somehow doesn't work because
of that piece of kryptonite in my pocket.
-John
Software QA Engineer
GTE Internetworking
Burlington, MA, USA
next prev parent reply other threads:[~2000-04-04 15:50 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
2000-04-04 15:46 ` John Grossi [this message]
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=NBBBLHNFOKNOPEBNMKGFGEAPEBAA.jgrossi@bbnplanet.com \
--to=jgrossi@bbnplanet.com \
--cc=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).