Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users
Date: Tue, 07 Sep 2010 22:06:03
Message-Id: 1283897135.4629.3.camel@localhost.localdomain
In Reply to: Re: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users by dev-random@mail.ru
1 El mié, 08-09-2010 a las 01:44 +0400, dev-random@××××.ru escribió:
2 > On Tue, Sep 07, 2010 at 09:30:34PM +0000, Robin H. Johnson wrote:
3 > > This implies that the upstream is alive enough to fix it.
4 > >
5 > > I feel it should mean that the bug has been reported to upstream, and
6 > > that state is documented in the bug.
7 > >
8 > > If we keep every upstream bug open instead of closed, we'd have probably
9 > > another 2500 open bugs (5312 RESO/UPSTREAM in the history of Gentoo, and
10 > > I'm ballparking that 50% aren't actually fixed yet upstream).
11 >
12 > Bug may be a blocker. And marking it as RESOLVED/UPSTREAM you may
13 > unblock another bug (e.g. stabilization request) which should be still
14 > blocked because there is no fixed package in tree.
15 >
16
17 In most cases when it's really a blocker, bug will remain opened anyway
18 until solved or, if not possible, stabilization will be postponed.

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
[gentoo-dev] Re: RFC Bugzilla interaction guide for devs & editbugs users Duncan <1i5t5.duncan@×××.net>