Re: [Lilypond-auto] Issue 2777 in lilypond: Learning Manual has version 2.14.2 instead of 2.16.0

[lilypond]

Comment #4 on issue 2777 by address@hidden: Learning Manual has  
version 2.14.2 instead of 2.16.0
http://code.google.com/p/lilypond/issues/detail?id=2777

I'm testing a merge of stable/2.16 and translation branches, with updates  
of PO files, in branch translation-staging, and I was considering putting  
the following patch (which I finally didn't commit).

In both unstable and stable releases, I think that bumping PATCH_LEVEL in  
VERSION should be done just after the release has completed, which the CG  
states correctly, see  
http://grenouille.lilynet.net/lilypond-web/master/Documentation/contributor/minor-release-checklist.html.   
However, this same page of the CG tells to update VERSION_DEVEL and  
VERSION_STABLE in the post-release stage, which I think is wrong, and  
actually created the issue we're discussing: setting VERSION_DEVEL and  
VERSION_STABLE to the value they will be expected to have when the release  
has completed (i.e. if you're doing a stable release, set VERSION_STABLE to  
MAJOR_VERSION.MINOR_VERSION.PATCH_LEVEL that are currently in  
stalbe/2.16:VERSION, and VERSION_DEVEL to the last unstable version that  
you know to be already released) in the same commit as the release  
announcement sounds like a good idea.


diff --git a/VERSION b/VERSION
index ec5897b..3c90e6d 100644
--- a/VERSION
+++ b/VERSION
@@ -1,7 +1,7 @@
 PACKAGE_NAME=LilyPond
 MAJOR_VERSION=2
 MINOR_VERSION=16
-PATCH_LEVEL=0
+PATCH_LEVEL=1
 MY_PATCH_LEVEL=
-VERSION_STABLE=2.14.2
-VERSION_DEVEL=2.15.95
+VERSION_STABLE=2.16.1
+VERSION_DEVEL=2.17.1