From 59b9e196e9f9fca969d5d49be9d81a59ef007a95 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Wed, 13 Jan 2010 12:02:27 +0000 Subject: [PATCH] Doc: CG: some notes about releases. --- Documentation/contributor/release-work.itexi | 21 ++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi index 36b6d211ea..068500dbdd 100644 --- a/Documentation/contributor/release-work.itexi +++ b/Documentation/contributor/release-work.itexi @@ -311,3 +311,24 @@ LANGUAGE LISTS once they've finished all "priority 1" translation items. +UPDATING A RELEASE ( x.y.z-a, where a>1 ) + +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' + +4. manually upload them. good luck figuring out the rsync +command(s). Hints are in test-lily/ + + -- 2.39.5