On Tue, Feb 9, 2010 at 9:27 AM, Dmytro O. Redchuk <brownian....@gmail.com> wrote: > So, currently CG requires the Bug Meister (Valentin now) to accept new > issue.
We should replace "the Bug Meister" by "any member of the Bug Squad" in this sentence. James and you are both able to decide when an issue can be Accepted. A "New" issue is just an issue that hasn't been reviewed and accepted by a bug squad member. If you're really unsure whether an issue should be accepted or not, you may mark it as New and ask me about my opinion, but hopefully in time you'll never have to. Most of the time, "Accepting" an issue is just checking whether it's a duplicate or not, if the report is correct and reproducible, etc. It doesn't require special skills (otherwise I wouldn't be in charge ;). > CG, 7.1 Introduction to issues: > ... 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*. Similarly, I'd say "developers and Bug Squad members only"/ > So, most probably, these CG sections should be corrected. In this case > it's obvious to mention that i can easily assign wrong priorities... > «If unsure, set to "Low"»?.. Just for someone to reassign?-) > «If unsure, set to "Critical"»?.. Just to be sure that it will be > reassigned?-) If unsure, I always use "Medium". "Critical" is for segmentation faults, etc. Things that make LilyPond unusable. "Low" is for when the output could be nicer, but is still readable by a musician. Cheers, Valentin _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
