1 |
On Thursday 02 March 2006 14:09, Mark Loeser wrote: |
2 |
> Paul de Vrieze <pauldv@g.o> said: |
3 |
> > * Just because breaking policy breaks a QA tool, but is guaranteed to |
4 |
> > never break itself (formatting policy, like space vs. tab etc.) |
5 |
> > does not increase the severity of the breakage. |
6 |
> |
7 |
> I had hoped something like this would have just been understood to not |
8 |
> be too severe, since it doesn't really break anything but coding |
9 |
> standards. |
10 |
> |
11 |
> > * Before any enforcement is possible, QA must establish a well |
12 |
> > supported (debated on dev-) exception policy. While it were nice if |
13 |
> > exceptions are not needed, reality is that they can not be avoided. |
14 |
> > Therefore there must be an exception policy. |
15 |
> |
16 |
> I'm not sure what you mean here. You mean for each instance? In |
17 |
> general? In general can be difficult since it leaves a lot of things |
18 |
> up for interpretation. For each instance, 99% of the time an |
19 |
> acceptable interim solution should be able to be achieved between the |
20 |
> QA team and the maintainer. In situations where we can't figure out |
21 |
> how to best address the situation, opening the discussion up to -dev |
22 |
> may help, but in the end it should come down to an agreement between |
23 |
> the maintainer and the team. |
24 |
|
25 |
The policy should be general. It could be something like "Developer and QA |
26 |
discuss the exception and the solution to be used. If they do not agree |
27 |
the council.... . In any case when an exception is made, appropriate bugs |
28 |
are created, including a bug to request a feature that makes the |
29 |
exception unneeded. When the requested feature is available and stable, |
30 |
the exception becomes invalid and the feature must be used instead." |
31 |
|
32 |
My idea is that QA can not enforce controversial things before such a |
33 |
policy exists. Otherwise exceptions stay only a theoretical possibility, |
34 |
and arguments continue. |
35 |
|
36 |
Paul |
37 |
|
38 |
-- |
39 |
Paul de Vrieze |
40 |
Gentoo Developer |
41 |
Mail: pauldv@g.o |
42 |
Homepage: http://www.devrieze.net |