Doc: CG: minor adds to bug guidelines and releases.

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index df1a6cb2bc371548fd99347b231be35178850004..13932d1c9f8ee1db2e6decb66c2f5999cce83ceb 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -204,6 +204,11 @@ documentation available from:
 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:
@@ -215,7 +220,6 @@ step 2 in our bug reporting guidelines:
   @uref{http://lilypond.org/website/bug-reports.html}
 @end example
 
-
 @item
 If anything is unclear, ask the user for more information.
 

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index bc75eaf62301f4b021024acdc0198b674f8fbabb..fcaa95d2ad4c5b8c24b6ecc4362c8709814f696b 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -284,6 +284,16 @@ make a link from the old unstable to the next stable in
 lilypond.org's /doc/ dir.  Keep all previous unstable->stable doc
 symlinks.
 
+Also, make the old docs self-contained -- if there's a redirect in
+/doc/v2.12/Documentation/index.html , replace it with the
+index.html.old-2.12 files.
+
+The post-2.13 docs will need another way of handling the
+self-containment.  It won't be hard to whip up a python script
+that changes the link to ../../../../manuals.html to
+../website/manuals.html , but it's still a 30-minute task that
+needs to be done before 2.16.
+
 @item
 doc auto redirects  to v2.LATEST-STABLE