On Fri, Oct 28, 2011 at 08:23:18AM +0200, David Kastrup wrote: > Graham Percival <gra...@percival-music.ca> writes: > > > incidently, I saw that I increased the version number properly > > after 2.15.15; all that's was missing is a new release. > > PACKAGE_NAME=LilyPond > MAJOR_VERSION=2 > MINOR_VERSION=15 > PATCH_LEVEL=16 > MY_PATCH_LEVEL= > VERSION_STABLE=2.14.2 > VERSION_DEVEL=2.15.15
yes, that looks correct at the time that I sent that email. At that time, the latest release was 2.15.15. The PATCH_LEVEL in git was 2.15.16, and _DEVEL was 2.15.15. I have just release 2.15.16, and VERSION now has PATCH_LEVEL=17 and _DEVEL= 2.15.16. I have pushed, and both git status and gitk report no unpushed commits. > My python/convertrules.py aims for 2.15.17 however, as the > \makeStringTuning change is already committed: Committed in your personal branch, rather than master? yes, that sounds correct. You should now either put that commit up for review, or else push it to dev/staging. (incidently, I can't do a merge --ff-only from master to staging right now, so we could use your help there). Once it's in staging (whether or not it went through a countdown), it will get added to master, and once that's done, I will make another release. - Graham _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
