This is a very dev oriented definition (so I'm fine with that :)). At
least it's precise.
I think one of the most conflicting areas between BUG and IMPROVEMENT
is things you could define as "limitations". Things that behave is a
way the user does not like too much but are hard to improve for
technical reasons or lack of time.
On Thu, Feb 2, 2017 at 3:30 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
The story:
* Some reporter (Anca in this case) reported the issue
https://jira.xwiki.org/browse/XWIKI-13947 as a bug
* Caty modified it as an improvement
* I didn’t quite agree and also consider it to be a bug
So I think it would be healthy that we agree about the difference of bug vs improvement.
This is not meant as a flamewar but more as a discussion to see if we could reach an
agreement. If not, then so be it, we won’t have a common agreement.
Here’s my POV and what I consider a bug is:
"A bug is something that was NOT wanted by the developer. It's not related to
its severity and there can be minor bugs and important bugs”
I realize that another definition could be “A bug is any behaviour that a user consider
not normal” but I find this more hazy and subject to interpretation so I prefer my first
definition.
For Caty a bug is “[…]broken/not working behaviour.” but that definition is not precise
enough IMO since for me the issue in XWIKI-13947 is a broken behavior (I consider that the
right behavior is to have the same top and bottom margin for boxes) and thus would match
Caty’s rule.
I also consider that there can be all types of bugs: visual bugs, performance bugs,
feature bugs, etc and thus I don’t consider that visual issues are always improvements and
never bugs.
So an improvement would be about doing something differently than in the way it was
voluntarily implemented.
WDYT?
Thanks
-Vincent
--
Thomas Mortagne