1 @c -*- coding: us-ascii; mode: texinfo; -*-
7 * Minor release checklist::
8 * Major release checklist::
12 @node Development phases
13 @section Development phases
15 There are 2.5 states of development for LilyPond.
19 @item @strong{Stable phase}:
20 Starting from the release of a new major version @code{2.x.0}, the
21 following patches @strong{MAY NOT} be merged with master:
24 @item Any change to the input syntax. If a file compiled with a
25 previous @code{2.x} version, then it must compile in the new
28 @item New features with new syntax @emph{may be committed},
29 although once committed that syntax cannot change during the
30 remainder of the stable phase.
32 @item Any change to the build dependencies (including programming
33 libraries, documentation process programs, or python modules used
34 in the buildscripts). If a contributor could compile a previous
35 lilypond @code{2.x}, then he must be able to compile the new
40 @item @strong{Development phase}:
41 Any commits are fine. Readers may be familiar with the term
42 @qq{merge window} from following Linux kernel news.
45 @item @strong{Release prep phase}:
46 FIXME: I don't like that name.
48 A new git branch @code{stable/2.x} is created, and a major release
53 @item @code{stable/2.x branch}:
54 Only translation updates and important bugfixes are allows.
57 Normal @qq{stable phase} development occurs.
61 If we discover the need to change the syntax or build system, we
62 will apply it and re-start the release prep phase.
66 This marks a radical change from previous practice in LilyPond.
67 However, this setup is not intended to slow development -- as a
68 rule of thumb, the next development phase will start within a
69 month of somebody wanting to commit something which is not
70 permitted during the stable phase.
74 @node Minor release checklist
75 @section Minor release checklist
77 A @qq{minor release} means an update of @code{y} in @code{2.x.y}.
79 email brief summary to info-lilypond
83 @node Major release checklist
84 @section Major release checklist
86 A @qq{major release} means an update of @code{x} in @code{2.x.0}.
90 * write release notes. note: stringent size requirements for
91 various websites, so be brief.
93 * write preface section for manual.
95 * submit pots for translation : send url of tarball to
96 translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
100 * Check all 2ly scripts.
102 * Run convert-ly on all files, bump parser minimum version.
104 * Make FTP directories on lilypond.org
107 - Make new table in download.html
109 - add to documentation list
111 - revise examples tour.html/howto.html
113 - add to front-page quick links
115 - change all links to the stable documentation
117 - doc auto redirects to v2.LATEST-STABLE
122 comp.os.linux.announce
129 info-lilypond@@gnu.org
131 linux-audio-announce@@lists.linuxaudio.org
132 linux-audio-user@@lists.linuxaudio.org
133 linux-audio-dev@@lists.linuxaudio.org
135 tex-music@@icking-music-archive.org
138 abcusers@@blackmill.net
140 rosegarden-user@@lists.sourceforge.net
142 noteedit-user@@berlios.de
144 gmane.comp.audio.fomus.devel
145 gmane.linux.audio.users
146 gmane.linux.audio.announce
147 gmane.comp.audio.rosegarden.devel
154 http://www.apple.com/downloads
155 harmony-central.com (news@@harmony-central.com)
156 versiontracker.com [auto]