From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFD: Bugzilla in general & bug triaging
Date: Tue, 15 May 2007 22:27:58 -0500 [thread overview]
Message-ID: <464A7A3E.9050905@gmail.com> (raw)
In-Reply-To: <f29dkh$o3v$1@sea.gmane.org>
Rolf Leggewie wrote:
> I have asked and been granted greater powers on bugzilla. There are
> features which we don't use yet but which could aid in establishing a
> sane workflow while rendering unnecessary the current clutches and
> ad-hoc fixes.
>
> Bugzilla will be upgraded soon and no structural changes will be made
> until that is completed. But that leaves us some good time to think
> about how this should be enhanced.
>
two quibbles about the recent change in bugtracker
1) aligning left wastes lot of space on the right of the screen. I think
the old "centered" scheme looks better.
2) "the Words field cannot be empty. You have to enter at lease on word
in your search criteria". This is inconvenient for me to just browser
the bugs.
> Things I'd like to see
> * confirmation flags
> * better documentation of workflow status (need to define it first)
> * assigning bugs (or if you prefer "Hey, please take a look")
> * link to some bug searches like the ones I send about 5 minutes ago
> on the entry page
> * entry page clean-up (why two search fields?)
>
> * removal of dead stuff (ZaurusKernel, Familiar)
>
better hide them (sort of a archive in case some people want to dig into
those) than remove
> Please add to the list. The most important point is the second. That
> is what we should discuss.
>
I agree on the necessity of the second point. Please have a list of
best-practice/workflow rules (whatever they are) and hide the additional
irrelevant features. A clean and uncluttered interface is also desirable.
Gordon
prev parent reply other threads:[~2007-05-16 3:31 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
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 [this message]
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=464A7A3E.9050905@gmail.com \
--to=xjqian@gmail.com \
--cc=openembedded-devel@lists.openembedded.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