Mailinglist Archive: opensuse-factory (649 mails)

< Previous Next >
Re: [opensuse-factory] openSUSE BugHunting 2017
On 2017-08-02 00:16, Per Jessen wrote:
Carlos E. R. wrote:

On 2017-08-01 23:42, Per Jessen wrote:
Carlos E. R. wrote:

On 2017-08-01 14:18, Per Jessen wrote:
Carlos E. R. wrote:

On 2017-08-01 13:34, Per Jessen wrote:
Carlos E. R. wrote:

If you do that, then why should I bother to report new bugs if
nobody is going to care, even read it? :-/

Carlos, for the same reason we always have - in the vain hope a
might be picked up and fixed. Having a report closed as "no
longer under maintenance" is not just "somewhat frustrating", it
is extremely frustrating, but what else do you propose we do?
Pursuing a bug for a product that cannot be updated is pointless,
but obviously the reporter is more than welcome to reopen if the
problem persists in a maintained version.

For starters, give some thought to the bug. Did somebody read it,
or was it sent to a non existing maintainer? Then send to the
current maintainer, and let him read it and decide.

I think the number of open reports alone prohibit that approach,
however nice it is.

So if the bug was sent to an incorrect destination, nobody will see
that and new bugs on that area will suffer the same fate in another
five years.

The reporter will also be notified.

But he will not have a clue what happened.

It will all be in the report?

No. We are talking here of bugs that get assigned to a person that is no
longer at the project, an email that doesn't exist, a mail list with no
subscribers. There is no way the reporter can find out what happened,
only an insider.

Now, if that bug is simply closed without investigation, the next bug
that gets reported in that area will suffer the same fate: bit bucket.

If the number of unhandled bugs is so big, there is something very
wrong going on.

The number of open reports is that big, yes. See the original

Well, IMHO the important thing is to find out why and correct that
situation... then bub count will slowly diminish.

Why - not enough people that deal with bug reports.
Correction - get more people to deal with bug reports.

Or developers that ignore bug reports.

In the meantime, try to reduce the mountain by at least closing reports
on versions no longer under maintenance.

If it is done summarily, that will piss the reporter a lot.

If the bug does not exist on the new release, why was he not told that
issue was solved? He might as well not report at all, issues are solved
or not solved on their own after some years. Don't report, because
nothing will change by reporting.

Don't close summarily. If it takes months to do it properly, so be it:
do it properly.

Cheers / Saludos,

Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)

< Previous Next >
Follow Ups