2,569
edits
Changes
Jump to navigation
Jump to search
Line 165:
Line 165: − You don't understand the fix provided, + − explain what you think the fixed means or what you have tried+ + − + − + − * patch_in_cvs [-+?]+ − So a new RPM will shortly be available, untested presumably+ − Great, a solution not a problem, lets make it clear+ + + − You have made a suggestion or added code you would like comment on+ + + + +
→Bugzilla flags
* need_help_to_verify [-+?]
* need_help_to_verify [-+?]
"I don't understand how to verify this bug - please help" - a request to
the dev team or other verifiers to have another look at the bug. Please
say what you don't understand and what you've looked at.
* package_maintained_upstream
* package_maintained_upstream
The package is maintained in an upstream repository. We won't be
patching it locally. We've deemed it to be not important enough for us
to fork the package, and so we'll wait for the fix to propogate from
upstream. In these case we like to add a URL to the upstream bug report.
* patch_or_code_attached [-+?]
* patch_or_code_attached [-+?]
There is either a patch or some code attached to this bug. Attached may
actually mean inline in the text, but the bug contains some code change
which someone says works for them.
* Review [-+?]
* Review [-+?]
This bug/change needs review by someone else. This is used by the dev
team for "Do you think this change is a good one?"
* [-+?]
Set the flag to ? to say someone needs to look at it