public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Bugzilla etiquette suggestions
Date: Sun, 12 Feb 2006 23:39:47 +0000	[thread overview]
Message-ID: <43EFC743.1070106@gentoo.org> (raw)
In-Reply-To: <pan.2006.02.12.22.53.36.218999@cox.net>

Duncan wrote:
>> 2. Be careful with INVALID resolutions
>>
>> The term invalid _is_ harsh in bugzilla context, so make sure you write 
>> a quick thankful-sounding comment to go with it.
> 
> I like all the suggestions, but this one hits a particular sore spot, as I
> had it happen to me, with I think my second Gentoo bug filing.

I'm glad that you can relate to it - reassures me that I'm not pulling 
this out of thin air :)

 > What made
> things worse is that the filing was after my arch team had asked for
> volunteers to perform specific tests (multilib-strict), and I had gone to
> significant effort to do so, having builds die that would otherwise have
> completed successfully.
> 
> As it happens, the bug /was/ valid, and was eventually resolved

That's another issue which is worth thinking about. I'm just as bad at 
this myself - if I can close a bug report without doing any work (i.e. 
the case for most INVALID bugs) then it's almost like a small personal 
victory.

We should also try not to jump the gun so much in this kind of situation.

Thanks for the feedback, if bugzilla ever drives you to suicide I will 
be sure to file a bug report at the official Bugzilla bugzilla so that 
it can be corrected :)

Daniel

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-02-12 23:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 21:11 [gentoo-dev] Bugzilla etiquette suggestions Daniel Drake
2006-02-12 21:43 ` Henrik Brix Andersen
2006-02-12 23:24   ` Daniel Drake
2006-02-13  0:57     ` Ferris McCormick
2006-02-13  8:09       ` Ciaran McCreesh
2006-02-13  9:50     ` [gentoo-dev] " Duncan
2006-02-13 16:11       ` Daniel Drake
2006-02-13 17:17         ` [gentoo-dev] " Duncan
2006-02-16 11:02       ` [gentoo-dev] " Michael Cummings
2006-02-13 10:51     ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2006-02-13 16:30       ` Daniel Drake
2006-02-12 22:53 ` [gentoo-dev] " Duncan
2006-02-12 23:39   ` Daniel Drake [this message]
2006-02-13  8:13   ` Ciaran McCreesh
2006-02-13 17:26     ` Richard Fish
2006-02-14  2:54       ` lnxg33k
2006-02-13 18:39   ` Simon Stelling
2006-02-13 18:49     ` Ciaran McCreesh
2006-02-13 19:00       ` Patrick McLean
2006-02-13 19:06         ` Marien Zwart
2006-02-13 19:07       ` Grobian
2006-02-13 19:21         ` Ciaran McCreesh
2006-02-13 19:29           ` Grobian
2006-02-13 20:02             ` Carsten Lohrke
2006-02-13 20:13               ` Grobian
2006-02-13 19:36       ` Diego 'Flameeyes' Pettenò
2006-02-14 13:03     ` [gentoo-dev] " Duncan
2006-02-14 13:18       ` Stephen P. Becker
2006-02-15  7:48         ` [gentoo-dev] " Duncan
2006-02-12 22:58 ` [gentoo-dev] " Marien Zwart
2006-02-12 23:32   ` Daniel Drake
2006-02-13  8:16     ` Ciaran McCreesh
2006-02-13 19:12       ` Donnie Berkholz
2006-02-13  4:06 ` Ned Ludd
2006-02-17 14:20   ` Shyam Mani
2006-02-17 14:11 ` Shyam Mani

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=43EFC743.1070106@gentoo.org \
    --to=dsd@gentoo.org \
    --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