Am 03/22/2016 12:30 AM, schrieb Pedro Lino:
On Mon, Mar 21, 2016 at 10:32 PM, Marcus<marcus.m...@wtnet.de> wrote:
Am 03/21/2016 10:36 PM, schrieb Kay Schenk:
[top posting]
Thanks for all the help with this and for the new NONE for
target release. Hopefully, it will be used sparingly
assuming we us e RESOLVED-FIXED as only for issues in which
an actual commit is used. Issue 126828 has now been changed
to UNCONFIRMED. How to differentiate UNCONFIRMED from
RESOLVED--NOT AN ISSUE will be a challenge. Hopefully, this
can be clarified to our QA helpers
I repeat my suggestion for another resolution status as it maybe got lost
in people's inboxes.
My suggestion is to create a RESOLVED - RESOLVED status. Maybe still to
close to RESOLVED - FIXED, but then let's see if there are better wordings.
There is already a final status after RESOLVED - FIXED. It's VERIFIED -
FIXED. It is set after a QA member verifies that the fix actually solved
the problem and that it does not occur in the RC.
Hope this helps.
no, that's not what I meant. ;-)
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.
Therefore I suggested a new status RESOLVED - RESOLVED.
I hope this explains it better.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
