[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: protocol: closing bugs

On Mon, Oct 11, 1999 at 05:44:33PM +1000, Hamish Moffatt wrote:
> On Fri, Oct 08, 1999 at 01:23:22PM -0700, Sean 'Shaleh' Perry wrote:
> > That said, yes, I would keep them open until potato is released.
> I thought protocol was to close bugs fixed in the latest upload,
> even though they are not fixed in stable? I suspect the BTS
> would have many more entries if we couldn't close bug reports
> until a new release is made.

Please see my wishlist bug #46434 against bugs.debian.org.

I have made a proposal that would eliminate problems with closing bugs
in unstable, when the bugs still exists in stable...

I previously mentioned this on debian-private, too, but it seems
to have got lost in with all the other messages sent at the time.
Because nothing in it is private, I have attached that message here.
Brian May <bam@snoopy.apana.org.au>
--- Begin Message ---
[ quoted stuff truncated as this was posted on debian-private ]

Some maintainers deliberately keep bug reports open. Why? Assume
somebody reports a bug in stable (after all most users should use stable
and not unstable). The maintainer fixes the bug, *in unstable* and
closes the bug.

However, other people also encounter the same bug, in stable. They check
for active bug reports - there aren't any, so they refile a new bug

This means the maintainer must keep the bug report open, even though
the problem has been fixed.

Another issue is that unstable users have to look through all bugs
reports, even those that a specific to stable. Similarly, stable users
have to look through all bug reports, even those that only apply to

eg, (made up example) do any problems exist in package XYZ for slink?
Yes - there are 20 bugs reports. After detailed reading - hang on - all
of those are related to libc6.1, and as such do not apply to slink.

All bug reports currently apply to a single version of the package.
I think it would be better if a bug report could apply to a list of
versions (possibly a NULL list if it is determined it isn't a bug at
all). When you open a bug, it automatically sets the "start version",
and the bug applies from all version past that version. When a bug
report is closed, it sets the "end version" so the bug report will apply
yo all versions between the start and end version.

This would enable a user to query the bug system "are there any
know bugs in version X.Y.Z of package XYZ"?? This could be
automated in a script that automatically checks what version
is installed.

I have reported this as wishlist item #46434 against bugs.debian.org.
I may have missed some details either here, so please check
there if in doubt. If I missed any details there, please feel
free to add them...

Issues I haven't addressed:
- list of versions that bug applies to may not always be sequential,
eg if a good stable version is uploaded after several unstable
releases (eg security bug).
- reassigning bug reports.

I feel that this sought of feature in the BTS would be really important,
especially now that bug reports are persistant.
Brian May <bam@snoopy.apana.org.au>

Please respect the privacy of this mailing list.

To UNSUBSCRIBE, email to debian-private-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--- End Message ---

Reply to: