CG: Use latest convert-ly for LSR updates (fix 2346) (issue 5696069)

[janek . lilypond]

Reviewers: ,

Message:
Please review.

I'm very busy with GSoC now, so if you identify deficiencies, please
write verbose changes you want done.  Otherwise i will update it
somewhere in March, sorry :(

Janek

Description:
CG: Use latest convert-ly for LSR updates (fix 2346)

Suggested by Thomas Morley:
Use convert-ly from latest development release for LSR updates

Please review this at http://codereview.appspot.com/5696069/

Affected files:
  M Documentation/contributor/lsr-work.itexi


Index: Documentation/contributor/lsr-work.itexi
diff --git a/Documentation/contributor/lsr-work.itexi  
b/Documentation/contributor/lsr-work.itexi
index  
1a64a55c8fbcb2d9c77d4cf2445069331abe6e12..8bb10bf1b0e6fc74afdd361ec86826037fbcfd6a  
100644
--- a/Documentation/contributor/lsr-work.itexi
+++ b/Documentation/contributor/lsr-work.itexi
@@ -300,6 +300,32 @@ Download the latest snippet tarball, extract it, and  
run
 correct stable version.

 @item
+Make sure you use @code{convert-ly} from the latest available release to  
gain
+all advantages from the latest converting-rules-updates.
+
+Example:
+
address@hidden
+
address@hidden
+LSR-version: 2.12.2
+
address@hidden
+intended LSR-update to 2.14.2
+
address@hidden
+latest release 2.15.30
+
address@hidden itemize
+
+Use @code{convert-ly} from 2.15.30 and the following terminal
+command for all files:
+
address@hidden
+convert-ly -e -t2.14.2 *.ly
address@hidden example
+
address@hidden
 Copy relevant snippets (i.e., snippets whose version is equal to or less
 than the new version of LilyPond) from
 @file{Documentation/snippets/new/} into the tarball.