Page MenuHomePhabricator

Distinguish "ok" revision status between "looks ok" and "I've tested it and it works"
Closed, ResolvedPublic

Description

Sometimes a code change *looks* ok but has side effects or problems which become evident after actually trying it. It would be nice to have a little more confidence of whether something has been thoroughly poked or not.

Maybe another status level beyond "ok", or maybe a separate flag that indicates someone's actually tried it.


Version: unspecified
Severity: enhancement

Details

Reference
bz18134

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:35 PM
bzimport set Reference to bz18134.

What should it be called? "good"?

"tested" maybe... though should make sure that doesn't conflict with integration of data from automatic running of regression tests.

ayg wrote:

(that should be r48934, I guess)