From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8907 invoked from network); 4 Apr 2000 15:50:20 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 Apr 2000 15:50:20 -0000 Received: (qmail 1300 invoked by alias); 4 Apr 2000 15:50:11 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10473 Received: (qmail 1261 invoked from network); 4 Apr 2000 15:50:06 -0000 From: "John Grossi" To: "Bart Schaefer" , Subject: RE: Closing bugs (?) Date: Tue, 4 Apr 2000 11:46:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <1000404153917.ZM20523@candle.brasslantern.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal > 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