From: Paul Sokolovsky <pmiscml@gmail.com>
To: Junqian Gordon Xu <xjqian@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFD: Bugzilla in general & bug triaging
Date: Mon, 14 May 2007 12:06:30 +0300 [thread overview]
Message-ID: <1851689443.20070514120630@gmail.com> (raw)
In-Reply-To: <46482288.2040904@gmail.com>
Hello Junqian,
Monday, May 14, 2007, 11:49:12 AM, you wrote:
> Paul Sokolovsky wrote:
>> Hello Junqian,
>>
>> Monday, May 14, 2007, 11:08:03 AM, you wrote:
>>
>>
>>> Is it a problem if I replace the openembedded-issues@ with my email
>>> address in the Reassign to field? Does openembedded-issues still gets
>>> all the updates?
>>>
>>
>> As Rolf described in his mail, we do not reassign bugs in our
>> workflow - they keep being assigned to ML. That's corresponds to
>> the fact/reassures that we don't have bug owners in OE, and entire
>> community welcome to/works on any issue (which in turn is based on the
>> fact that we don't have dedicated engineers to resolve bugs).
> Paul,
> One benefit of reassigning the bug to myself is that I can click the "My
> Bug" button and list all my filed and self-assigned bugs, instead of
> remembering the bug number or relying on search.
I well understand benefits of assigning bugs, it's just the
fact that OE doesn't assign them (as as was mentioned, it's good, as
have psychological effect of welcoming everyone to work on things, not
think "well, that guy will fix it" or "oh, it's that guy's, I can't
touch it").
> I'm undoing the damages right now. But please let me know if there's an
> alternative to easily keep track of interested bugs. Well, maybe I'm
> too lazy.
You still better rely on search. And Bugzilla is a powerful
("enterprise-grade" ;-) ) tool, which allows you to do many things.
For example, that's how I have it set up: I add myself to cc: of the
interesting bugs (in full accordance to Rolf's RFD), then once made
an advanced search setup, which searches for my address in any email
field (reporter, cc, etc.), and saved it as saved search. Now, it's
the same one click as predefined "My Bugs" search. And you can have
number of saved searches, for machines of your interest, for software,
etc. - all one click away.
> Gordon
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-05-14 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 12:25 RFC: Bugzilla CC Field Graeme Gregory
2007-05-13 14:29 ` Koen Kooi
2007-05-13 14:33 ` RFD: Bugzilla in general & bug triaging Rolf Leggewie
2007-05-13 15:02 ` Koen Kooi
2007-05-13 15:15 ` Paul Sokolovsky
2007-05-14 8:08 ` Junqian Gordon Xu
2007-05-14 8:25 ` Paul Sokolovsky
2007-05-14 8:49 ` Junqian Gordon Xu
2007-05-14 9:06 ` Paul Sokolovsky [this message]
2007-05-14 9:18 ` Junqian Gordon Xu
2007-05-14 9:06 ` Koen Kooi
2007-05-14 10:16 ` Rolf Leggewie
2007-05-14 11:26 ` Paul Sokolovsky
2007-05-14 10:28 ` Rolf Leggewie
2007-05-14 13:28 ` Marcin Juszkiewicz
2007-05-16 3:27 ` Junqian Gordon Xu
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=1851689443.20070514120630@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=xjqian@gmail.com \
/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