Add `make-countdown-announcement.sh'.

[lilypond.git] / Documentation / contributor / issues.itexi

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index c9d19f5079ea44b023d1d1f37076636f6dfd5bc6..8fe73428eefb6b50f452ae211661ee47b77b943c 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -187,12 +187,12 @@ the currently-active Bug Squad member(s) can handle the message.
 
 @example
 Monday:    Eluze
-Tuesday:   Ralph
-Wednesday: Marek
-Thursday:  Joe Wakeling (soon)
-Friday:    Colin H
-Saturday:  Colin H
-Sunday:    Federico
+Tuesday:   Ralph Palmer
+Wednesday: Marek Klein
+Thursday:  Eluze
+Friday:
+Saturday:  Colin Campbell
+Sunday:    Federico Bruni
 @end example
 
 
@@ -854,7 +854,7 @@ status to @qq{patch-review} and emails the developer list.  If the patch
 fails, Patchy sets it to @qq{patch-needs_work} and notifies the developer list.
 
 @item
-The Patch Handler reviews the tracker periodically, to list patches
+The Patch Meister reviews the tracker periodically, to list patches
 which have been on review for at least 24 hours. The list is found at
 
 @smallexample
@@ -875,7 +875,7 @@ clear the @qq{send email} box to prevent sending notification for
 each patch.
 
 @item
-The Patch Handler sends an email to the developer list, with a fixed
+The Patch Meister sends an email to the developer list, with a fixed
 subject line, to enable filtering by email clients:
 
 @example
@@ -885,47 +885,31 @@ PATCH: Countdown to 20130113
 The text of the email sets the deadline for this countdown batch.  At
 present, batches are done on Tuesday, Thursday and Sunday evenings.
 
-The body of the email lists the patches grouped by patch type, and for
-each patch, shows the tracker issue number and title, with a link to
-the Rietveld item.  Copying the information from the website and pasting
-into the email gives a hyperlinked version of the information.
-
-@smallexample
-
-For 20:00 MST Tuesday January 8:
-
-Crash:
-    Issue 2990: \RemoveEmptyStaves in StaffGroup context crashes - R 7069044
-
-Defect:
-    Issue 677: \score markup confuses paper settings - R 7028045
-    Issue 3050: displayLilyMusic produced erroneous code for rightHandFinger arguments - R 7032045
-
-Documentation:
-    Issue 2952: Upgrade documentation of \once - R 7031053
-    Issue 3044: Dual license the files under mf/ using OFL. - R 6970046
-    Issue 3084: [DOC]Add "Known issue" in NR 1.2.1 about Scaling durations with rational numbers - R 7071044
-
-Enhancement:
-    Issue 3061: make \articulate handle colon-type tremolos - R 7033045
-    Issue 3082: Patch: Let ChordNameVoice use the same performers as Voice - R 7054043
-    Issue 3083: Patch: Chord change detection in fretboards should depend on placements, not notes - R 7062043
-    Issue 2983: assertion failed with \glissando - R 6625078
+To create the countdown announcement, use the
+@code{make-countdown-announcement.sh} script, which takes the
+deadline date, and optionally your name.  Follow the instructions
+provided:
 
+@example
+cd $LILYPOND_BUILD_DIR
+../scripts/auxiliar/make-countdown-announcement.sh "Jan 1, 2001" James
+@end example
 
-Cheers,
-Colin
+The script produces an announcement that is easily readable in all
+email clients.  Also, whenever a new contributor submits a patch,
+you will be prompted to add the new username and author name to
+the script itself, and then commit those changes to the main git
+repository.
 
-@end smallexample
 
 @item
-On the scheduled countdown day, the Patch Handler reviews the
+On the scheduled countdown day, the Patch Meister reviews the
 previous list of patches on countdown, with the same procedure and
 criteria as before.  Patches with no controversy can be set to
 @qq{patch-push} with a courtesy message added to the comment block.
 
 @item
-Roughly at six month intervals, the Patch Handler can list the
+Roughly at six month intervals, the Patch Meister can list the
 patches which have been set to @qq{patch-needs-work} and send the
 results to the developer list for review.  In most cases, these
 patches should be marked @qq{patch-abandoned} but this should come