command(s). Hints are in test-lily/
+MAKING A RELEASE -- NEW INFO
+
+(wow, I really need to stop being so messy here. Will clean it up
+after 2.13.11; I need a chance to test these instructions)
+
+1. switch to the release branch:
+ git checkout release/unstable
+
+1b. get latest changes
+ git merge origin
+
+2. make a release announcement by editing:
+ Documentation/web/news-front.itexi
+(and maybe moving the oldest news item to news-old.itexi)
+
+3. upload:
+ git push release/unstable
+
+4. make GUB as "normal"
+ make LILYPOND_BRANCH=release/unstable -f lilypond.make doc
+(if this works, make it the default for GUB)
+
+5. upload git, etc.
+
+6. update VERSION, commit, push.
+ VERSION = what you just did +0.0.1
+ DEVEL_VERSION = what you just did (i.e. is now online)
+ STABLE_VERSION = what's online
+
+7. switch back to master and merge the changes
+ git merge release/unstable
+(FIXME: only if the release announcement+version are the only
+changes; if you hacked more stuff, then try cherry-picking)
+
+8. (for now) manually upload
+ Documentation/pictures/out-www/
+ Documentation/web/ly-examples/out-www/
+to $HOME/media/pictures .../ly-examples on lilypond.org
+
+