bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Updated CG 7 Issues -- new policies for Bug Squad


From: Dmytro O. Redchuk
Subject: Re: Updated CG 7 Issues -- new policies for Bug Squad
Date: Fri, 4 Jun 2010 10:05:03 +0300
User-agent: Mutt/1.5.20 (2009-06-14)

On Thu 03 Jun 2010, 20:52 Graham Percival wrote:
> Hi Bug Squad and others,
> 
> I've updated CG 7 Issues:
> http://lilypond.org/doc/v2.13/Documentation/contributor/issues

7.1 Introduction to issues and the Bug Squad

1. "If the behaviour is expected, the user should be told to read the
documentation"...

Isn't it a task for "Support" team? If i asked smth. like mentioned here in
bug-lilypond, i would consider as a quite normal answer "please ask this in
lilypond-user" (well, case-by-case, surely, and in a good and polite way, of
course, but anyway?..).

... "or asked to clarify how he misread the docs and how the docs
could be improved."

Well... Yes.


7.2 Issue classification

"The classification of what counts as a bug vs. feature request, and the
priorities assigned to bugs, are a matter of concern *for developers only*.
The Bug Squad should classify issues according to the guidelines given by
developers."

Well... How Bug Squad members should ask/obtain those guidelines for every
particular issue? Should be add "7.7 For developers only" ?-)

(I'm sure, _any_ policy and practice guided by an ideal policy may lead to
some discussions.. After all procedures were completed and guidelines were
obtained.)

Moreover, "Priority (mandatory)" subsection already contains some (quite
clear) guidelines --- so, why this restriction (... should classify issues
according to the ...)? Well.. "highly embarrassing items" is a bit fuzzy, but
practice is the best guideline here, probably.

So, i would propose to leave "The Bug Squad should classify issues according
to the guidelines given below" or like that.

> I think those will be possible with the expanded Bug Squad.

> When you review the chapter, don't just nod and think "yeah,
> that's how I do stuff" -- ask yourself "when I was starting out,
> would I know what I was supposed to do after reading this?".

7.3 Adding issues to the tracker

I would mention smth like "Added issue is always better then missed. We aware
of that fact that some issues may be "Invalid"; anyway in every case false
negatives are better then missed negatives. In a case Bug Squad member would
add invalid issue or mis-classify one, she (he) will be corrected in a nice
way." (and a nice picure of a gun aka Mutt/1.5.18 (2008-05-17)) :O)

> 
> Cheers,
> - Graham

-- 
  Dmytro O. Redchuk



reply via email to

[Prev in Thread] Current Thread [Next in Thread]