Re: [platform-ui-dev] What does it mean for a bug to be fixed?

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

There will always be cases that aren't
100% clear, but your points go into the right direction. See my comments
below.

> I would suggest the following:

> - The person who filed the bug
has final say on whether or not it has been fixed.
In general, yes, but if the person is
not able to provide steps, he has no final say on WORKSFORME. Same applies
to WONTFIX, unless the person wants to provide a fix.

> - In the absence of a definitive
statement from the bug requester, the bug is fixed if and only if the steps
to reproduce still reproduce the behavior.
I guess you meant "no longer reproduce
the behavior". Yes, that should be the usual procedure.

> - The steps to reproduce are the
steps included in comment 0 along with any clarifications made by the person
who filed the bug.
From my experience most of the time
the steps aren't yet in comment 0 ;-). I would rather say: to mark a bug
fixed, at least the steps of the person who filed the bug, must be fixed.

> - Comments made by people other
than the one who filed the bug can't change what the bug is about nor the
criteria for considering it fixed.
Yes, unless the original bug reporter
agrees with the change of direction, Usually, including an update of the
bug summary.
 
> So I ask you: is bug 234744 fixed or not? Is it a dupe or not?
> It's still reproducible from the
original steps and the person who filed it says it's not fixed. However,
subsequent comments by other people discussed different (prerequisite)
topics, which were either addressed by a patch in the bug or are a dupe
of another bug.
It is not fixed, but there is a very
similar bug open and targeted for 4.6. I've marked it as duplicate of that
one.

> Can people other than the bug requester
change the focus of a bug, or should this be considered bug hijacking?
In most cases I'd consider it bad practice.

Dani




From:      
 Stefan Xenos <sxenos@xxxxxxxxxx>
To:      
 "Eclipse Platform
UI component developers list." <platform-ui-dev@xxxxxxxxxxx>
Date:      
 24.02.2016 19:43
Subject:    
   [platform-ui-dev]
What does it mean for a bug to be fixed?
Sent by:    
   platform-ui-dev-bounces@xxxxxxxxxxx

---

https://bugs.eclipse.org/bugs/show_bug.cgi?id=234744

I been having a disagreement on a bug, which brings up
a philosophical question: what does it mean for a bug to be fixed? I was
wondering where we stand on this since, IMO, we should have clear guidelines.

Some possibilities:

1. If the bug contains steps to reproduce, the bug is
fixed if and only if those steps no longer reproduce the bug.

2. If the bug contains a patch, the bug is fixed if and
only if that patch has been merged.

3. The bug is fixed if and only if the person who filed
it agrees that it is fixed.

4. If the majority of comments in a bug discuss some problem,
the bug is fixed if and only if that problem has been addressed, even if
that problem is different from the one originally reported.

I would suggest the following:
- The person who filed the bug has final say on whether
or not it has been fixed.
- In the absence of a definitive statement from the bug
requester, the bug is fixed if and only if the steps to reproduce still
reproduce the behavior.
- The steps to reproduce are the steps included in comment
0 along with any clarifications made by the person who filed the bug.
- Comments made by people other than the one who filed
the bug can't change what the bug is about nor the criteria for considering
it fixed.

So I ask you: is bug 234744 fixed or not? Is it a dupe
or not?

It's still reproducible from the original steps and the
person who filed it says it's not fixed. However, subsequent comments by
other people discussed different (prerequisite) topics, which were either
addressed by a patch in the bug or are a dupe of another bug.

Can people other than the bug requester change the focus
of a bug, or should this be considered bug hijacking?

  - Stefan
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev