Paul de Vrieze <[EMAIL PROTECTED]> said: > * Just because breaking policy breaks a QA tool, but is guaranteed to > never break itself (formatting policy, like space vs. tab etc.) does not > increase the severity of the breakage.
I had hoped something like this would have just been understood to not
be too severe, since it doesn't really break anything but coding standards.
> * Before any enforcement is possible, QA must establish a well supported
> (debated on dev-) exception policy. While it were nice if exceptions are
> not needed, reality is that they can not be avoided. Therefore there
> must be an exception policy.
I'm not sure what you mean here. You mean for each instance? In
general? In general can be difficult since it leaves a lot of things up
for interpretation. For each instance, 99% of the time an acceptable
interim solution should be able to be achieved between the QA team and
the maintainer. In situations where we can't figure out how to best
address the situation, opening the discussion up to -dev may help, but
in the end it should come down to an agreement between the maintainer
and the team.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpa7xQtkRfX0.pgp
Description: PGP signature
