[ << Release work ] | [Top][Contents] | [ Modifying the Emmentaler font >> ] |
[ < Minor release checklist ] | [ Up : Release work ] | [ Release extra notes > ] |
11.3 Major release checklist
A “major release” means an update of x
in 2.x.0
.
Main requirements
These are the current official guidelines.
- 0 Critical issues for two weeks (14 days) after the latest release candidate.
Potential requirements
These might become official guidelines in the future.
- Check reg test
- Check all 2ly scripts
-
Check for emergencies the docs:
grep FIXME --exclude "misc/*" --exclude "*GNUmakefile" \ --exclude "snippets/*" ????*/*
-
Check for altered regtests, and document as necessary:
git diff -u -r release/2.FIRST-CURRENT-STABLE \ -r release/2.LAST-CURRENT-DEVELOPMENT input/regression/
Housekeeping requirements
Before the release:
- write release notes. note: stringent size requirements for various websites, so be brief.
- Run convert-ly on all files, bump parser minimum version.
-
Update lilypond.pot:
make -C $LILYPOND_BUILD_DIR po-replace mv $LILYPOND_BUILD_DIR/po/lilypond.pot po/
-
Make directories on lilypond.org:
~/download/sources/v2.NEW-STABLE ~/download/sources/v2.NEW-DEVELOPMENT
- Shortly after the release, move all current contributors to previous contributors in ‘Documentation/included/authors.itexi’.
-
Delete old material in ‘Documentation/changes.tely’, but
don’t forget to check it still compiles! Also update the version
numbers:
@node Top @top New features in 2.NEW-STABLE since 2.OLD-STABLE
-
Website:
-
make a link from the old unstable to the next stable in
lilypond.org’s ‘/doc/’ dir. Keep all previous unstable->stable
doc symlinks.
Also, make the old docs self-contained – if there’s a redirect in ‘/doc/v2.OLD-STABLE/Documentation/index.html’ , replace it with the ‘index.html.old-2.OLD-STABLE’ files.
The post-2.13 docs will need another way of handling the self-containment. It won’t be hard to whip up a python script that changes the link to ‘../../../../manuals.html’ to ‘../website/manuals.html’, but it’s still a 30-minute task that needs to be done before 2.16.
-
doc auto redirects to
v2.NEW-STABLE
-
add these two lines to ‘Documentation/web/server/robots.txt’:
Disallow: /doc/v2.OLD-STABLE/ Disallow: /doc/v2.NEW-DEVELOPMENT/
-
if needed, update the htaccess redirections
(
/latest/
,/stable/
etc.) in ‘Documentation/web/server/lilypond.org.htaccess’. - if needed, add a link to the previous stable version’s announcement, list of changes and contributors acknowledgements to the ‘Attic’ page, in ‘Documentation/web/community.itexi’.
-
make a link from the old unstable to the next stable in
lilypond.org’s ‘/doc/’ dir. Keep all previous unstable->stable
doc symlinks.
Unsorted
- submit po template for translation: send url of tarball to coordinator@translationproject.org, mentioning lilypond-VERSION.pot
-
update links to distros providing lilypond packages? link in:
‘Documentation/web/download.itexi’
This has nothing to do with the release, but it’s a “periodic maintenance” task that might make sense to include with releases.
-
Send announcements to...
News:
comp.music.research comp.os.linux.announce comp.text.tex rec.music.compose
Mail:
info-lilypond@gnu.org info-gnu@gnu.org planet@gnu.org linux-audio-announce@lists.linuxaudio.org linux-audio-user@lists.linuxaudio.org linux-audio-dev@lists.linuxaudio.org consortium@lists.linuxaudio.org planetccrma@ccrma.stanford.edu tex-music@tug.org rosegarden-user@lists.sourceforge.net denemo-devel@gnu.org
Web (forums):
imslpforums.org abcusers (Yahoo group) canorus (Github? Freenode IRC?) musescore.org/forum reddit.com/lilypond linuxquestions.org Slashdot
Web (websites and aggregators):
lilypond.org https://savannah.gnu.org/news/submit.php?group_id=1673 freshmeat.sourceforge.net linuxtoday.com lxer.com fossmint.com fsdaily.com freesoftwaremagazine.com lwn.net hitsquad.com/smm in French: linuxfr.org; framalibre.org
[ << Release work ] | [Top][Contents] | [ Modifying the Emmentaler font >> ] |
[ < Minor release checklist ] | [ Up : Release work ] | [ Release extra notes > ] |