bug-lilypond
[Top][All Lists]
Advanced

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

Re: checking CG 7. issues


From: James Bailey
Subject: Re: checking CG 7. issues
Date: Sat, 6 Feb 2010 23:59:14 +0100


On 06.02.2010, at 21:34, Graham Percival wrote:

Hi guys,

Could you check over CG 7. Issues ?
http://lilypond.org/doc/v2.13/Documentation/contributor/issues

In particular, is there any info that I've told you (privately or on
the mailing list) that isn't in there?  Is there anything that you
know now, that you didn't know before you started being in the Bug
Squad, that you wish you could have read in this chapter?  etc.

I'm thinking about advertising for more Bug Squad people in 2-3 weeks,
so we should make sure the CG is in good condition.

Also, please note that although **I'll** be advertising for more Bug
Squadders, I don't want to train any volunteers myself.  Instead, I
want to pair newbies up with you three people.  So the better you can
make the CG chapter, the fewer questions you'll have to answer.  :)
(or at least, if somebody asks something that's covered in the CG, you
can just point to the CG section rather than typing an answer from
scratch)


Oh, that reminded me: Dmytro, if there's any new bug reports, pick one
and try adding it to the tracker.  Read CG 7.2 in detail before you do
that.  I expect that you'll encounter a few problems, but this will be
a good test of the CG on this topic.

Cheers,
- Graham

The descriptions for Priority-medium and Priority-Low are a bit vague, Priority-Postponed is understandable, if one knows the history of development on things like Ancient Notation/MIDI, but understanding the difference between these things, especially medium and low, would be very helpful. Also, currently, the link to bug reports isn't working. And 7.6 Finding the cause of a regression may be a job that a non-programmer can do, but it should be notated that one needs to understand git, which most non-programmers are probably not familiar with.




reply via email to

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