Release protocol

PREPARATION

• Make a list of most important changes.
• Write an release announcement incorporating this list.
• Update the list of extensions
• Update list of CC licenced images etc
• Put all images through the compressor (https://github.com/i7/kerkerkruip/issues/41#issuecomment-13217381)

FINAL BUILD (@curiousdannii)

• Put correct version in game title
• Generation info must be set to false.
• Glimmr must be commented in and Extended Debugging commented out.
• Build a release version.

POST-BUILD (@curiousdannii)

• Rename the file to Kerkerkruip.gblorb. (Otherwise the .ini won't work.)
• Final test whether it runs in gargoyle.

PACKAGING (@curiousdannii)

• Put game file and ini file in a zip archive.
• Create OS specific installers
• If it's a major release then create a release branch now (so that the installers are included)

RELEASE

• Upload the file to lilith.cc.
• Update the lilith.cc Kerkerkruip page.
• Upload new version to IF Archive.

ANNOUNCEMENTS

• Announce at Kerkerkruip.org
• Announce at Gaming Philosopher.
• Announce at IFDB.
• Announce at intfiction.org.
• Announce at Temple of the Roguelike forum.
• Update page at roguebasin, and add to new releases.
• Announce at audiogames.net.
• If the Bay12 topic remains alive: announce it in there.
• Add release notes to IFWiki.
• Update Kerkerkruip wiki?