From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO]
Date: Sun, 10 Jul 2005 16:34:58 +0100 [thread overview]
Message-ID: <20050710163458.7e23cba2@snowdrop.home> (raw)
In-Reply-To: <42D13F9C.3040502@ieee.org>
On Sun, 10 Jul 2005 11:32:44 -0400 "Nathan L. Adams" <nadams@ieee.org>
wrote:
| > Again, Gentoo is not a large corporation or Debian.
|
| I don't see how Gentoo's status (or rather lack thereof) as a
| corporation or Debian has anything to do with encouraging peer review.
You're taking methods from a "how your typical oversized software
engineering bloatware project works" situation and trying to apply them
outside of their domain.
| > The assumption is
| > that the majority of fixes are done correctly the first time, and
| > this assumption is valid.
|
| I don't see how you could prove that assumption. If you can, please do
| so.
Experience. I receive bug mail for a heck of a lot of bugs. I see how
many of them are indeed correctly resolved when they are marked as such.
| > Hence, the default behaviour is to mark bugs as
| > RESOLVED, with reopening being an entirely legitimate and encouraged
| > response for those occasional instances where the resolution was not
| > sufficient.
| >
|
| There are plenty of devs who don't share in the viewpoint that
| reopening bugs is legitimate and should encouraged (although I agree
| it is and should be). I base opinion that on some of the kicking and
| screaming I've seen on bugzilla in the past. ;)
No, that kicking and screaming is reserved for when bugs are reopened
inappropriately.
--
Ciaran McCreesh
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-10 15:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 3:52 [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO] Jory A. Pratt
2005-07-09 15:11 ` Nathan L. Adams
2005-07-09 15:16 ` Ciaran McCreesh
2005-07-09 16:04 ` Nathan L. Adams
2005-07-09 16:08 ` Nathan L. Adams
2005-07-09 19:39 ` Marco Matthies
2005-07-09 19:56 ` Nathan L. Adams
2005-07-09 19:59 ` Ciaran McCreesh
2005-07-09 20:39 ` Marco Matthies
2005-07-10 7:39 ` R Hill
2005-07-10 12:13 ` Duncan
2005-07-10 7:30 ` R Hill
2005-07-10 13:49 ` Nathan L. Adams
2005-07-10 14:18 ` Jon Portnoy
2005-07-10 15:08 ` Nathan L. Adams
2005-07-10 15:19 ` Ciaran McCreesh
2005-07-10 15:32 ` Nathan L. Adams
2005-07-10 15:34 ` Ciaran McCreesh [this message]
2005-07-10 22:18 ` Nathan L. Adams
2005-07-10 15:39 ` Diego 'Flameeyes' Pettenò
2005-07-10 19:37 ` Maurice van der Pot
2005-07-10 22:30 ` Nathan L. Adams
2005-07-10 19:27 ` R Hill
2005-07-10 22:20 ` Nathan L. Adams
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 2:08 [gentoo-dev] New Bugzilla HOWTO Chris White
2005-07-07 18:49 ` Simon Stelling
2005-07-07 20:15 ` [gentoo-dev] " Duncan
2005-07-08 11:42 ` [gentoo-dev] Closing bugs [was: New Bugzilla HOWTO] Nathan L. Adams
2005-07-09 1:37 ` [gentoo-dev] " Duncan
2005-07-09 1:50 ` Mike Frysinger
2005-07-09 3:46 ` Nathan L. Adams
2005-07-09 10:11 ` Martin Schlemmer
2005-07-09 14:54 ` Nathan L. Adams
2005-07-09 15:11 ` Jon Portnoy
2005-07-09 16:00 ` Nathan L. Adams
2005-07-09 16:02 ` Stephen P. Becker
2005-07-09 16:20 ` Nathan L. Adams
2005-07-10 0:00 ` Jon Portnoy
2005-07-10 1:06 ` Nathan L. Adams
2005-07-10 2:19 ` Jory A. Pratt
2005-07-10 3:23 ` Nathan L. Adams
2005-07-10 8:59 ` Daniel Drake
2005-07-09 15:44 ` Gregorio Guidi
2005-07-09 16:04 ` Nathan L. Adams
2005-07-09 22:53 ` R Hill
2005-07-10 13:55 ` Nathan L. Adams
2005-07-10 14:33 ` Daniel Drake
2005-07-10 15:14 ` Nathan L. Adams
2005-07-10 15:33 ` Daniel Drake
2005-07-10 14:44 ` Jason Stubbs
2005-07-10 10:18 ` Henrik Brix Andersen
2005-07-10 13:14 ` Nathan L. Adams
2005-07-10 16:23 ` Henrik Brix Andersen
2005-07-09 17:00 ` Mike Frysinger
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=20050710163458.7e23cba2@snowdrop.home \
--to=ciaran.mccreesh@blueyonder.co.uk \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox