From: dev-random@mail.ru
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users
Date: Wed, 8 Sep 2010 01:44:59 +0400 [thread overview]
Message-ID: <20100907214459.GA11425@laptop> (raw)
In-Reply-To: <robbat2-20100907T212225-495258166Z@orbis-terrarum.net>
On Tue, Sep 07, 2010 at 09:30:34PM +0000, Robin H. Johnson wrote:
> This implies that the upstream is alive enough to fix it.
>
> I feel it should mean that the bug has been reported to upstream, and
> that state is documented in the bug.
>
> If we keep every upstream bug open instead of closed, we'd have probably
> another 2500 open bugs (5312 RESO/UPSTREAM in the history of Gentoo, and
> I'm ballparking that 50% aren't actually fixed yet upstream).
Bug may be a blocker. And marking it as RESOLVED/UPSTREAM you may
unblock another bug (e.g. stabilization request) which should be still
blocked because there is no fixed package in tree.
next prev parent reply other threads:[~2010-09-07 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 8:32 [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users Robin H. Johnson
2010-09-06 8:39 ` Dirkjan Ochtman
2010-09-06 12:38 ` Alex Legler
2010-09-06 15:31 ` Michael Weber
2010-09-06 16:07 ` [gentoo-dev] " Christian Faulhammer
2010-09-06 21:24 ` Ryan Hill
2010-09-06 12:10 ` Christian Faulhammer
2010-09-06 12:36 ` Alex Legler
2010-09-07 20:47 ` [gentoo-dev] " Róbert Čerňanský
2010-09-07 21:30 ` Robin H. Johnson
2010-09-07 21:43 ` Andreas K. Huettel
2010-09-07 21:44 ` dev-random [this message]
2010-09-07 22:05 ` Pacho Ramos
2010-09-07 22:53 ` [gentoo-dev] " Duncan
2010-09-08 4:44 ` Ryan Hill
2010-09-10 16:32 ` [gentoo-dev] " Jeroen Roovers
2010-09-11 7:17 ` [gentoo-dev] " Duncan
2010-09-11 13:43 ` Jeroen Roovers
2010-09-11 21:58 ` [gentoo-dev] " Róbert Čerňanský
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=20100907214459.GA11425@laptop \
--to=dev-random@mail.ru \
--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