Am 03/22/2016 12:52 AM, schrieb Pedro Lino:
It's not about to draw the line between issues that are resolved and
verified solutions. It's about to differentiate issues that are in the real
application and therefore need to be fixed in the source code. Here we use
(or better should use) RESOLVED - FIXED.
But what about issues that are also reporting a problem but the solution
(if there is any) is somewhere else? RESOLVED - FIXED doesn't fit, RESOLVED
- NOT_AN_ISSUE also not.
Why not use the same nomenclature as the "sibling project"? RESOLVED -
NOTOURBUG
in general it's OK to look for other projects how they handle such
problems. But NOTOURBUG sounds really ignorant and a bit offensive - at
east in my ears. When I think about the users that reporting such issues
and mostly they think it's important because they cannot go on with
their work, then they deserve a more meaningful status name.
Dennis has made a good suggestion where I'll go on with answering.
I believe Apache QA needs a flowchart such as
https://wiki.documentfoundation.org/images/c/c4/Unconfirmed_Bugs_Status_Flowchart_Version_0.1.pdf
https://wiki.documentfoundation.org/images/c/cb/Unconfirmed_Bugs_Status_Flowchart.odg
I'm pretty sure we have a similar flow chart somewhere in the depths of
our Wiki. But yes, in general this would help to understand how the
issue statuses are working together.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org
