@enumerate
+@item
+Wait until your gmail account is listed in:
+
+@example
+@uref{http://code.google.com/p/lilypond/people/list}
+@end example
+
@item
Sign in to google code by clicking in the top-right corner of:
@uref{http://code.google.com/p/lilypond/issues/list}
@end example
+You cannot log if you have Google Sharing
+@uref{http://www.googlesharing.net/} enabled.
+
@item
Go to your @qq{Profile}, and select @qq{Settings}.
Any email sent with your gmail address in the @code{To:} or
@code{CC:} fields should go to a @code{bug-answers} folder.
+When setting up your filtering rules, be aware that Google Code
+might use different versions of your email address, such as ones
+ending in @code{@@googlemail.com} or @code{@@gmail.com}.
+
@item
Any other email either from, or CC'd to,
@subsubheading Daily schedule
+The Bug Meister is omitted from the daily schedule.
+
@example
-Sunday: Valentin
+Sunday: Colin
Monday: Dmytro
Tuesday: James Bailey
Wednesday: Ralph
-Thursday: Phil Holmes
-Friday: Urs Liska, Patrick
+Thursday: Patrick
+Friday: Urs
Saturday: Kieren
@end example
or ask the lilypond-user mailing list.
@end example
+@item
+If the email mentions @qq{the latest git}, or any version number
+that has not yet been officially released, forward it to
+@code{lilypond-devel}.
+
@item
If a bug report is not in the form of a Tiny example, direct the
user to resubmit the report with this response:
@uref{http://lilypond.org/website/bug-reports.html}
@end example
-
@item
If anything is unclear, ask the user for more information.
@item
Checking all issues: we try to mark each Issue @q{fixed} when we
fix it, but occasionally one or two issues will slip through the
-cracks. It is therefore good to check all Issues. If you see the
+cracks. It is therefore good to check all Issues. If you see the
same (broken) output as the initial report, then simply post a
@qq{Problem still exists in 2.x.y} message to the issue.
@item
Type-Scripts: problem or desired feature in the non-build-system
scripts. Mostly used for convert-ly, lilypond-book, etc.
+
@item
Type-Enhancement: a feature request for the core program. The
distinction between enhancement and defect isn't extremely clear;
@itemize
@item
-Priority-Critical: lilypond segfaults, or a regression occurred
-within the last two stable versions. (i.e. when developing 2.13,
-any regression against 2.12 or 2.10 counts)
+Priority-Critical: LilyPond segfaults, a regression against a
+previous stable version or a regression against a fix developed
+for this version. This does not apply where the @qq{regression}
+occurred because a feature was removed deliberately - this is not
+a bug.
@item
-Priority-High: highly embarrassing items, and any regression
-against a version earlier than two stable versions (i.e. when
-developing 2.13, any regression against 2.8 or earlier). This
-level is also used for issues which produce no output and fail to
-give the user a clue about what's wrong.
+Priority-High: An issue which produces output which does not
+accurately reflect the input (e.g. where the user would expect
+an accidental, but none is shown) or which produces aesthetically
+poor output in a situation which could be expected to crop up
+frequently in real-world music. It should not be used where the
+problem can be avoided with a simple workaround. It can also
+be used to flag where new code in a development version is not
+functioning as it should. This level is also used for issues
+which produce no output and fail to give the user a clue about
+what's wrong.
@item
-Priority-Medium: normal priority.
+Priority-Medium: Normal priority - use this as the default.
@item
-Priority-Low: less important than normal.
+Priority-Low: A minor problem which produces slightly undesirable
+output, or which will only occur in contrived examples, or which
+is very easily worked around.
@item
Priority-Postponed: no fix planned. Generally used for things
-like Ancient notation, which nobody wants to touch.
+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 (optional)
@end itemize
-If you particularly want to add an label not in the list, go
+If you particularly want to add a label not in the list, go
ahead, but this is not recommended.
@item
If the issue has a notation example which fits in one system,
-generate a small @file{bug@/.preview@/.png} file with:
+generate a small @file{bug.preview.png} file with:
@example
lilypond -dpreview bug.ly
@item
If the issue has an example which requires more than one system
-(i.e. a spacing bug), generate a @file{bug@/.png} file with:
+(i.e. a spacing bug), generate a @file{bug.png} file with:
@example
lilypond --png bug.ly
@end example
@item
-If the issue requires multi-page output, then generate a
-@file{bug@/.pdf} file with the normal:
+If the issue requires one or two pages of output, then generate a
+@file{bug.png} file with the normal:
@example
lilypond --png bug.ly
@end example
+@item
+If the issue cannot be shown with less than three pages, then
+generate a @file{bug.pdf} file with:
+
+@example
+lilypond --pdf bug.ly
+@end example
+
+Note that this is likely to be extremely rare; most bugs should fit
+into the first two categories above.
+
+
@end itemize
@item
projects / lilypond.git / blobdiff