102027 - Create keyword "UIComplete" to replace "Correctness"

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[selmer (gone)]

Asa and I discussed what happened to the correctness keyword and how it became
too dilute to be useful.  The original intent was to capture bugs about UI
elements that were directly broken or had not been implemented.  Therefore, we
think the closest approximation would be to call that keyword "UIComplete".

Here's my cut at the definition:

Use this keyword when the UI exposes a feature that is either unusably broken or
not implemented.  The purpose of this keyword is to make these UI shortfalls
very visible when deciding whether or not the product is ready to ship.

Comment 1

[Asa Dotzler [:asa]]

what about "removeUI" ?

Use this keyword when the UI exposes a feature that is either unusably broken or
not implemented.  The purpose of this keyword is to make these UI shortfalls
very visible when deciding whether or not the product is ready to ship. Example:
"View|Headers|All does nothing so menuitem should be hidden."

--Asa

Comment 2

[selmer (gone)]

Hmm.  I was hoping that the keyword wouldn't imply a solution.  Maybe UIComplete
fails at that too.  For these bugs, we tend to want to get the fix so it works
unless we're out of time or it's low priority.  In the cases where we're
removing it, we usually file a new bug for that action since it's a temporary
fix.  Maybe it should be called brokenUI :-)

I admit I don't have a good name for it, I'll take whatever you can come up with...

Comment 3

[timeless]

uibroken? uiunimplemented?

Comment 4

[timeless]

ok those suck. uiDisconnect?

Comment 5

[Asa Dotzler [:asa]]

I think that useless-ui is pretty close to what we're looking for. We'll see :)

Comment 6

[timeless]

vrfy fixed. sounds good enough