Debian Bug report logs - #158434
bugs.debian.org: ChangeLog closes handling should be changed

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Gerfried Fuchs <alfie@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bugs.debian.org: ChangeLog closes handling should be changed

Date: Tue, 27 Aug 2002 08:48:31 +0200

Package: bugs.debian.org
Severity: wishlist

        Hi there!

 With the addition of the testing distribution we have new problems:
Bugs are closed in unstable but flow more or less slowly (due to
dependency problems) into testing, but are due to the uploads into
unstable long closed.

 What we need is a change here: Bugs should just be closed in unstable.
How to do this?  They should be rather be tagged <sarge> than be closed
by an upload to unstable.  Not unconditionally, of course.  The version
of the bugreport should be compared with the version currently in
testing.  Some sort of algorithm not too complex but able to handle most
of the cases shouldn't be too hard to do (yes, I volunteer to help
there).

 Secondly, the testing scripts should be tweaked, too.  They should
check the differences between the current changelog.Debian and the one
of the version that is going to flow in from unstable and close the
bugreports tagged <sarge>.  Why only those?  To avoid messages tagged
sid that where retagged sid because of problebugreports tagged <sarge>.
Why only those?  To avoid messages that were retagged sid because of
problems that are still in effect in unstable.

 Of course these sugguestions are not foolproof -- but the current
situation is neither.  I sugguest these changes to make the BTS a better
place to track bugs.  Current situation is far from optimal.  We
currently state that there isn't a bug anymore just by closing it with
an upload to unstable.  The fact is that is still is active in testing
and the BTS should live up to that fact.

 I hope that these sugguestion will hit some open ears.  I'm not really
sure if this is the best sugguestion, but it's the one idea I currently
came up with.  Feel free to comment on it, I guess discussion on
debian-devel (*without* the copy to the BTS directly) would be a good
idea, I am thinking of scanning the responses and mail summaries into
the BTS to keep the bugreport current.  If you like, Cc: me offlist if
really needed, I am not subcribed to debian-devel, but I'll watch the
discussion through both the webarchives and news:linux.debian.devel (and
answer from there -- need to finish my setup wrt/ that anyway ,).

 Thanks, and I hope some of the inner circle like the idea.
Alfie
-- 
php ist an sich ne recht nutzlose sprache wenn da nicht soviele dinge so
einfach drin moeglich waeren
                    -- Getty in #debian.de

Message #18 received at 158434@bugs.debian.org (full text, mbox, reply):

From: Josip Rodin <joy@gkvk.hr>

To: 158434@bugs.debian.org

Subject: addendum

Date: Thu, 29 Aug 2002 13:09:44 +0200

[Message part 1 (text/plain, inline)]

Hi,

Since elmo's yawning, I figured I was definitely missing something.

David Harris was kind enough to provide me with the relevant IRC log, which
I'm attaching for the record.

It seems that I was basing my conclusions on a false premise that Alfie's
ideas wouldn't actually be ignored here. Oh well :)

-- 
Joy

[bugs.log (text/plain, attachment)]

Message #25 received at 158434-done@bugs.debian.org (full text, mbox, reply):

From: Colin Watson <cjwatson@debian.org>

To: 46434-done@bugs.debian.org, 105776-done@bugs.debian.org, 158434-done@bugs.debian.org

Subject: Version tracking implemented

Date: Mon, 18 Jul 2005 12:44:58 +0100

Version tracking has been implemented on bugs.debian.org (see
debian-devel-announce). No doubt there will be some teething problems,
but it essentially finally closes these bugs. :-)

As far as #105776 goes, version-tracking-aware expiry isn't done yet,
but we won't be turning bug expiry back on again until it is.

Cheers,

-- 
Colin Watson                                       [cjwatson@debian.org]

Send a report that this bug log contains spam.