lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] Issue 3807 in lilypond: Add instructions on maintaining


From: lilypond
Subject: [Lilypond-auto] Issue 3807 in lilypond: Add instructions on maintaining the \version string in doc files
Date: Mon, 13 Jan 2014 16:41:47 +0000

Status: Accepted
Owner: tdanielsmusic
Labels: Type-Documentation

New issue 3807 by tdanielsmusic: Add instructions on maintaining the \version string in doc files
http://code.google.com/p/lilypond/issues/detail?id=3807


There is nothing in the CG about the \version
string in documentation files, particularly the
need to update it when adding code which uses
recently changed syntax.  This is more important
now that update-with-convert-ly no longer updates
it unconditionally when a new version is issued
(see Issue 3675).

Something along these lines is needed (nod to
David K):

"If you want to add stuff _not_ consistent with the
version header, you should

a) run convert-ly on the file (which should, if
   everybody did proper maintenance, not change
   anything apart from bumping the version header)
b) add the new code
c) make the version number match the new code if
   it does not already do so."

This should go into a new section between the
current 5.4.1 and 5.4.2.

Trevor

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]