[Top-Posting]
OK, as there were no further comments and no real disagree I'll create a
new RESOLVED - NOCODEFIX resolution status. This status should be set
when an issue was solved with no change in the source code (e.g., user
requests or how-to questions).
For every fix that touches the source code please use as always the
RESOLVED - FIXED resolution status.
Marcus
Am 03/26/2016 10:58 AM, schrieb Marcus:
Am 03/26/2016 10:50 AM, schrieb Andrea Pescetti:
Marcus wrote:
Am 03/26/2016 12:13 AM, schrieb Andrea Pescetti:
If the aim is to create less confusion, all proposals I've seen have
the
result of bringing more confusion! So:
I don't see why this brings more confusion. It's the opposite, one
status for "resolved with a code fix" and the other for "resolved
somehow else".
It brings more confusion since it would need to be explained explicitly
(because DONE or MANAGED would apply, looking purely at their meaning,
to a code fix too, and it's only a convention that we use them for
"no-code" fixes only).
maybe, but the whole BZ can be confusing - especially for normal users. ;-)
> And if we have more intuitive options I feel this would be better.
Do you have any idea in mind?
It doesn't have to be "NOCODE", but it should be
something that means "nothing to do with code", and DONE does not
really
convey the right meaning here.
Then NOCODEFIX sounds more concrete.
Yes, NOCODEFIX sounds good too. Again, so long as it is a word that a
developer cannot be mistaken into choosing instead of FIXED, it will be
OK for me. What we want to avoid is that a developer accidentally uses
DONE for a code fix and the issue is suddenly not listed in QA and
similar.
I got the idea to rename FIXED into FIXEDINCODE. Unfortunatelly, it's a
default and therefore a non-changeable name. :-(
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org
