Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaran.mccreesh@×××××××××××××.uk>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO]
Date: Sun, 10 Jul 2005 15:19:03
Message-Id: 20050710161905.64c0f091@snowdrop.home
In Reply to: Re: [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO] by "Nathan L. Adams"
1 On Sun, 10 Jul 2005 11:08:41 -0400 "Nathan L. Adams" <nadams@××××.org>
2 wrote:
3 | Maybe as a start, the Developer's Guide can be revised to state that:
4 |
5 | "Ideally any bug that a fix is submitted for should be verified and
6 | peer reviewed. It should be verified by the reporter or another user.
7 | If the reporter or another user are unable or unwilling to verify the
8 | fix, the Team Lead should take responsibility for the verification.
9 | Ideally, all bug fixes should be peer reviewed by the Team Lead and/or
10 | other team members before the bug is marked as RESOLVED.
11
12 Again, Gentoo is not a large corporation or Debian. The assumption is
13 that the majority of fixes are done correctly the first time, and this
14 assumption is valid. Hence, the default behaviour is to mark bugs as
15 RESOLVED, with reopening being an entirely legitimate and encouraged
16 response for those occasional instances where the resolution was not
17 sufficient.
18
19 --
20 Ciaran McCreesh
21 --
22 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO] "Nathan L. Adams" <nadams@××××.org>