1 @c -*- coding: us-ascii; mode: texinfo; -*-
7 * Minor release checklist::
8 * Major release checklist::
13 @node Development phases
14 @section Development phases
16 There are 2.5 states of development for LilyPond.
20 @item @strong{Stable phase}:
21 Starting from the release of a new major version @code{2.x.0}, the
22 following patches @strong{MAY NOT} be merged with master:
25 @item Any change to the input syntax. If a file compiled with a
26 previous @code{2.x} version, then it must compile in the new
29 @item New features with new syntax @emph{may be committed},
30 although once committed that syntax cannot change during the
31 remainder of the stable phase.
33 @item Any change to the build dependencies (including programming
34 libraries, documentation process programs, or python modules used
35 in the buildscripts). If a contributor could compile a previous
36 lilypond @code{2.x}, then he must be able to compile the new
41 @item @strong{Development phase}:
42 Any commits are fine. Readers may be familiar with the term
43 @qq{merge window} from following Linux kernel news.
46 @item @strong{Release prep phase}:
47 FIXME: I don't like that name.
49 A new git branch @code{stable/2.x} is created, and a major release
54 @item @code{stable/2.x branch}:
55 Only translation updates and important bugfixes are allows.
58 Normal @qq{stable phase} development occurs.
62 If we discover the need to change the syntax or build system, we
63 will apply it and re-start the release prep phase.
67 This marks a radical change from previous practice in LilyPond.
68 However, this setup is not intended to slow development -- as a
69 rule of thumb, the next development phase will start within a
70 month of somebody wanting to commit something which is not
71 permitted during the stable phase.
75 @node Minor release checklist
76 @section Minor release checklist
78 A @qq{minor release} means an update of @code{y} in @code{2.x.y}.
82 @item Add a news item to @file{Documentation/web/news-front.itexi}
84 @item Build release on GUB.
86 @item Check the regtest comparison in @file{uploads/webtest/} for
87 any unintentional breakage.
89 @item Check if the mingw build contains lilypad.exe; when you find
90 that it doesn't, rebuild @code{mingw::lilypond-installer}. Repeat
93 @item If any work was done on GUB since the last release, upload
94 binaries to a temporary location, ask for feedback, and wait a day
95 or two in case there's any major problems.
97 @item Upload release from GUB.
99 @item Update @file{VERSION} in lilypond git.
101 @item Wait a few hours for the website to update.
103 @item Email release notice to @code{info-lilypond}
108 @node Major release checklist
109 @section Major release checklist
111 A @qq{major release} means an update of @code{x} in @code{2.x.0}.
115 * write release notes. note: stringent size requirements for
116 various websites, so be brief.
118 * write preface section for manual.
120 * submit pots for translation : send url of tarball to
121 translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
125 * Check all 2ly scripts.
127 * Run convert-ly on all files, bump parser minimum version.
129 * Make FTP directories on lilypond.org
132 - Make new table in download.html
134 - add to documentation list
136 - revise examples tour.html/howto.html
138 - add to front-page quick links
140 - change all links to the stable documentation
142 - doc auto redirects to v2.LATEST-STABLE
144 - add these two lines to http://www.lilypond.org/robots.txt:
147 Disallow: /doc/v2.PREVIOUS-STABLE/
148 Disallow: /doc/v2.CURRENT-DEVELOPMENT/
154 comp.os.linux.announce
161 info-lilypond@@gnu.org
163 linux-audio-announce@@lists.linuxaudio.org
164 linux-audio-user@@lists.linuxaudio.org
165 linux-audio-dev@@lists.linuxaudio.org
167 tex-music@@icking-music-archive.org
170 abcusers@@blackmill.net
172 rosegarden-user@@lists.sourceforge.net
174 noteedit-user@@berlios.de
176 gmane.comp.audio.fomus.devel
177 gmane.linux.audio.users
178 gmane.linux.audio.announce
179 gmane.comp.audio.rosegarden.devel
186 http://www.apple.com/downloads
187 harmony-central.com (news@@harmony-central.com)
188 versiontracker.com [auto]
191 https://savannah.gnu.org/news/submit.php?group_id=1673 @c => planet.gnu.org
194 @node Making a release
195 @section Making a release
197 @subheading Technical notes
204 Run the following (from the gub/ dir):
211 If you do not have the previous release test-output tarball, download
212 it and put it in @code{regtests/}
220 @item If you're not user @code{graham} on the webserver, remove
221 the "t" from the rsync command in
222 @file{test-lily/rsync-lily-doc.py}
224 @item Probably run the following command. Look the output of
225 @code{make lilypond} in case it's different.
228 make lilypond-upload LILYPOND_BRANCH=master LILYPOND_REPO_URL=git://git.sv.gnu.org/lilypond.git