[ << Release work ]	[Top][Contents][Index][ ? ]			[ Build system notes >> ]
[ < Major release checklist ]		[  Up : Release work ]	[ Notes on builds with GUB > ]

11.4 Release extra notes

Regenerating regression tests

Regenerating regtests (if the lilypond-book naming has changed):

• git checkout release/lilypond-X.Y.Z-A
• take lilypond-book and any related makefile updates from the latest git.
• configure; make; make test
• tar -cjf lilypond-X.Y.Z-A.test-output.tar.bz2 input/regression/out-test/
• mv lilypond-X.Y.Z-A.test-output.tar.bz2 ../gub/regtests/
• cd ../gub/regtests/
• make lilypond

stable/2.12

If releasing stable/2.12, then:

• apply doc patch: patches/rsync-lily.patch (or something like that)
• change infodir in gub/specs/lilypond-doc.py from "lilypond.info" to "lilypond-web.info"

Updating a release (changing a in x.y.z-a)

Really tentative instructions, almost certainly can be done better.

1. change the VERSION back to release you want. push change. (hopefully you’ll have forgotten to update it when you made your last release)
2. make sure that there aren’t any lilypond files floating around in target/ (like usr/bin/lilypond).
3. build the specific package(s) you want, i.e.

   bin/gub mingw::lilypond-installer
   make LILYPOND_BRANCH=stable/2.12 -f lilypond.make doc
   bin/gub --platform=darwin-x86 \
     'git://git.sv.gnu.org/lilypond-doc.git?branch=stable/2.12'
   

   or

   build everything with the normal "make lilypond", then (maybe) manually delete stuff you don’t want to upload.

4. manually upload them. good luck figuring out the rsync command(s). Hints are in test-lily/

   or

   run the normal lilypond-upload command, and (maybe) manually delete stuff you didn’t want to upload from the server.

---

[ << Release work ]	[Top][Contents][Index][ ? ]			[ Build system notes >> ]
[ < Major release checklist ]		[  Up : Release work ]	[ Notes on builds with GUB > ]

<< Back to Documentation Index

LilyPond — Contributor’s Guide v2.21.0 (development-branch).