On 06/26/2012 10:48:04 AM, Don Armstrong wrote:
> On Mon, 25 Jun 2012, Karl O. Pinc wrote:
> > On 06/25/2012 02:10:18 PM, Don Armstrong wrote:
> > > On Mon, 25 Jun 2012, Karl O. Pinc wrote:
> > > > On 06/25/2012 12:48:41 PM, Don Armstrong wrote:
> > > > > On Mon, 25 Jun 2012, Karl O. Pinc wrote:
> > > > > > I don't see how to use the "Misc" option to set
> > > > > > dist=stable.
> > > >
> > > > > There is a drop down in the Misc section which you can use to
> set
> > > > > dist=stable. It is set to unstable by default.
> > I see it now, but "stable" is not one of the choices. :-(
>
> Fixed.
Ok. Thanks! It's now possible to find bugs
that are outstanding in stable using the web
page's interface.
I still have the gripe that it's not easy/obvious.
A trivial improvement is to add some verbiage to the
drop-downs in the Misc section so that it "reads".
Something like:
Bugs in <stable/unstable/etc drop down> that are <archived/
unarchived/etc. drop down>
A more serious problem is that, although I'll be
able to remember from now now, the interface
gives the casual user no guidance as to how
to find just the outstanding bugs.
First, there's the wording in the drop down. While
I'm sure there's good technical reasons to
have the "Include Bugs" drop-down read
"with pending state" the presence of the
word "pending" is, IMO, confusing.
While some of the bugs will have a pending
state, a lot of them will have finished
pending and have settled into an actual state.
I don't feel qualified to be confident that
this suggestion is a good one but perhaps
a better wording would leave off the word
"pending". The bug itself has the state,
it's the package that's "pending", or not.
Minimally, it'd be nice to have verbiage
on the right side of the page listing the
valid bug states. Something very similar
to what is already being done with valid
severities and valid tags. Of all my comments,
this is the one thing I would want to
see done before closing the this bug.
(You may of course feel differently.)
Ideally it'd be nice to have each section have
separate drop-downs, instead of a single
drop-down and a single text box. (Of course
that would likely require changes on the back-end.)
(Out of curiosity, does the BTS source live
anywhere or are people expected to get
the debbugs source package from experimental?)
Thanks for the work already done.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
