[Reportbug-maint] Bug#586155: reportbug: Add button to list bugs considered closed/archived in recent versions

Sandro Tosi morph at debian.org
Thu Jun 17 09:31:23 UTC 2010


Hello,

On Thu, Jun 17, 2010 at 00:53,  <trasuntopendiente at hotmail.com> wrote:
> Hello again
>
>> From: morph at debian.org
>> Date: Thu, 17 Jun 2010 00:23:52 +0200
>> Subject: Re: Bug#586155: reportbug: Add button to list bugs considered
>> closed/archived in recent versions
>> To: trasuntopendiente at hotmail.com; 586155 at bugs.debian.org
>>
>> Hello Elora,
>>
>> On Thu, Jun 17, 2010 at 00:13, Elora HRanma
>> <trasuntopendiente at hotmail.com> wrote:
>> > Package: reportbug
>> > Version: 4.10.2
>> > Severity: wishlist
>> >
>> > Hi, maintainers
>> >
>> > I'd love to see a button in the open bugs list which would let me browse
>> > those recently closed. It would prevent creating new bugs which should have
>> > actually been reopened.
>> > E.g.: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564117 which
>> > cannot be seen in reportbug, but is actually not fixed (it has been reopened
>> > in package libgtk-ruby1.8).
>> > If I have found, by using the web, the bug I want to reopen, but still
>> > want to use reportbug, it would be really helpful if it let me find it,
>> > using filters on closed bugs.
>>
>> Are you asking that reportbug get (somehow, implementative detail) the
>> list of recently (but how much is "recent"?) closed bug in the whole
>> BTS or for a single package?
>>
>
> I am talking about recent bugs for a given package. Somehow I missed that
> point in the description. "Recent" could be an option or a simple heuristic,
> like "archived less than one mont ago". Another possible meaning for
> "recent" would be "In the last X releases of the package", although the
> relevance of the release count varies heavily from one package to another.

so what you're asking is to show archived bugs along with bugs opened
and closed-but-not-archived. is that correct? If that's the case, and
I'm going to implement it, I will show all the archived bugs, not only
the "recent" ones.

So just clarify this and we'll see what we can do.

>> For a give pkg, you already have the list of resolved bugs not
>> archived (that happened after 30 days of inactivity).
>
> The bug I gave as an example was archived and reopened, through a new bug
> report, just 3 days after its archival. But maybe that was an extreme case,
> because 30 days should be more than enough to consider a bug closed. The way
> I see it, the user would initially have the list of open and unarchived bugs
> and, if the bug is not in there, press a "Show recently archived" button,
> which would trigger another query to BTS (select bugs of package archived in
> the last 30 days).
> Another possibility would be adding 2 radio buttons to the package selection
> screen, giving a (cumulative) choice on which bugs to retrieve: "Open and
> unarchived bugs", "Open, unarchived and recently archived".

Don't mix UI details with the concept you'd like to implement: it
bloats the text to read with few gain.

for the GTK+ there won't be any of such "box, radio buttons" or so,
just configure reportbug via ~/.reportbugrc , for command-line
version, there will be a command-line option.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi





More information about the Reportbug-maint mailing list