From 0ee6134e1ef4ad9040b2fcc9d51297c91af746d1 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Mon, 8 Feb 2010 00:43:39 +0000 Subject: [PATCH] Doc: CG: improve Issues. --- Documentation/contributor/issues.itexi | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi index 7c36c1e669..b8e59bc3a3 100644 --- a/Documentation/contributor/issues.itexi +++ b/Documentation/contributor/issues.itexi @@ -149,6 +149,14 @@ like Ancient notation, which nobody wants to touch. @end itemize +The difference between Priority-Medium and Priority-Low is not +well-defined, both in this policy and in practice. The only +answer we can give at the moment is @qq{look at existing items in +of the same type, and try to guess whether the priority is closer +to the Medium items or Low items}. We're aware of the ambiguity, +and won't complain if somebody picks a @q{wrong} value for +Medium/Low. + @subheading Opsys @@ -274,11 +282,11 @@ else about LilyPond development. Git has special functionality to help tracking down the exact commit which causes a problem. See the git manual page for -@code{git bisect}. - -This is a job that non-programmers can do; once a problematic -commit is identified, the programmers' job is much easier. In -fact, for most regression bugs, the majority of the time is spent -simply finding the problematic commit. +@code{git bisect}. This is a job that non-programmers can do, +although it requires familiarity with git, ability to compile +LilyPond, and generally a fair amount of technical knowledge. +Once a problematic commit is identified, the programmers' job is +much easier. In fact, for most regression bugs, the majority of +the time is spent simply finding the problematic commit. -- 2.39.2