As has been noted by several people, the current voting method has
some short comings on what should be voted -1, 0, or +1. In order to
help clarify what to vote, and when here are some guidelines that
should be useful.
Vote Non-exhaustive Reasons for vote
=====================================================================
-1 Program (or programs) do not work as expected.
Programs that link or require updated package do not work.
Bugs said to be fixed are not fixed.
Abrt reports a problem.
Installation/removal of RPM reports problems with scriplets, pre,
or post parts.
RPM spec changes have broken fedora guidelines.
---------------------------------------------------------------------
0 Program works as expected
Programs that link or require updated package work as expected.
Abrt does not indicate a problem after using.
Upgrade/installation does not indicate problems with rpm, spec
file, etc.
---------------------------------------------------------------------
+1 All of 0 reasons
Bugs known to user or bugs listed in reason for updated have been
tested and fixed (indicate in comments which bugs and test case
used.)
So for most users, when updating to updates-testing (or something
straight from bodhi/koji that has not been put in updates-testing) a 0
is the most likely response that should be given. A +1 should only be
given in cases where a specific test has been done (and should be
commented on. Ones without comments should be disregarded before pushing
to stable.)
As with any guidelines, this does not cover corner cases, emergencies,
or nitpicking to just find every problem possible. However it should
cover enough to make voting more useful.
If accepted, this may affect proposals that say that a certain number
of +1's are required before being pushed to production, but only after
testing and evaluation.
--
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
