From ScummVM :: Wiki
Revision as of 11:01, 26 September 2020 by Sev (talk | contribs) (→‎Binaries: update)
Jump to navigation Jump to search

How to make a ScummVM release.

This is work in progress and needs to be completed!

All examples are based on 1.7 and 1.7.0 version. Don't forget to adapt with the adequate version.


  • Making the release plan
  • Telling people about it, making sure everybody knows what is going on
  • Update the lists of files below, adding new engine data files and such

Branching for major release

  • Create a branch for the 2.2.x releases from master, named branch-2-2
    • git checkout -b branch-2-2 master
  • Increase version on branch-2-2 to 2.2.0pre (using devtools/; see below), and commit
    • devtools/ 2 2 0 pre
    • git commit -m "RELEASE: This is 2.2.0pre" -a
  • Create annotated tag desc/2.2.0pre on that commit and push
    • git tag -m "Mark 2.2.0pre" desc/2.2.0pre
    • git push origin tag desc/2.2.0pre branch-2-2:branch-2-2
  • Increase version on master to 2.3.0git, and commit
    • git checkout master
    • devtools/ 2 3 0 git
    • git commit -m "RELEASE: This is 2.3.0git" -a
  • Create annotated tag desc/2.3.0git on that commit and push
    • git tag -m "Mark 2.3.0git" desc/2.3.0git
    • git push origin tag desc/2.3.0git master
  • Update buildbot
    • Set scumm_branch_stable = "branch-2-2" in master.cfg around line 25.
    • Restart the buildbot as described here
  • Communication
    • Update IRC and Discord channel description
    • Write a mail to scummvm-devel


  • Ensure ADGF_TESTING/ADGF_UNSTABLE flags are correct for the release.
  • Identify release critical (show stopper) bugs and get people to fix them.
  • Identify other important bugs and get people to fix them.
  • Get even more people to fix all the other bugs, if possible :-).
  • Get people to do lots of testing, possibly by asking for help via a news item.
  • Collect all that information (e.g. in the Wiki). See Release Testing

Preparing the source

  • Browse 'git log' since the previous release and add all significant changes to the NEWS file
  • Make sure the translations.dat file is up to date. This file is automatically generated once per week (on Monday morning) and may need to be updated manually if changes to the translations occurred since the last Monday. Use make translations-dat to update the file (and then commit it if it was changed).
  • You have to update the versions in all relevant files. There is a script, devtools/ meant to help you with this. It will generate/update the following files:
    • base/internal_version.h
    • dists/macosx/Info.plist
    • dists/redhat/scummvm.spec
    • dists/scummvm.rc
  • Review the following documentation files for version and copyright year updates:
    • README(.md)
    • NEWS(.md)
  • Review the following port specific files for version updates:
    • backends/platform/ps2/README.PS2
    • backends/platform/psp/README.PSP
    • backends/platform/symbian/README
    • backends/platform/wince/README-WinCE.txt
    • backends/platform/ds/arm9/dist/readme_ds.txt
    • dists/win32/ScummVM.iss (AppVerName)
  • Review the release dates in the following port specific files:
    • dists/win32/scummvm.gdf.xml
  • Make sure package descriptions are up-to-date:
    • dists/redhat/scummvm.spec
  • Create MSVC project files in the release branch (for example branch-1-7-0, where the tarballs are created from)
    • make ideprojects
    • git commit -m "DISTS: Generated Code::Blocks and MSVC project files"
    • And last but not least don't forget to push the results to our github repo via "git push"
  • Make source tarballs, put them in the FRS directory.
    • There is a script devtools/, which creates them automatically.
    • Make sure that porters have write access to the release folder on FRS: chmod 775 <folder>
  • Add version to dists/macosx/scummvm_appcast.xml

Branching for minor releases

  • Create a branch for 1.7.0 from branch-1-7, named branch-1-7-0
    • git checkout -b branch-1-7-0 branch-1-7
  • Increase version on branch-1-7-0 to 1.7.0 and commit, push
    • devtools/ 1 7 0
    • Manually edit backends/platform/maemo/debian/changelog to reflect correct release date for 1.7.0 entry
    • git commit -m "RELEASE: This is 1.7.0" -a
    • git push origin branch-1-7-0:branch-1-7-0


  • Get porters to make binaries.
    • Porter must follow our filename convention, which goes like this: "scummvm-VERSION-PORT.EXTENSION". For example: "scummvm-1.1.0-macosx.dmg". Do not use special names like "EScummVM" or "ScummVMDS". The only exclusion from this requirement is Debian.
    • Porters should pass "--enable-release" to configure in case their port is using the configure/make based build system. If their port is not using the configure/make based build system they should make sure they properly define RELEASE_BUILD when compiling their release binary. It is also noteworthy that "--disable-debug" should be passed in order to remove debugging information from the binary.
    • Here is a list of files porters should include in their release archives:
      • AUTHORS
      • COPYING
      • NEWS(.md)
      • README(.md) (generic ScummVM one)
      • localized NEWS and README files (from doc/) (optional)
      • (from gui/themes directory) (if your port uses new GUI)
      • (from gui/themes directory) (if your port uses new GUI)
      • (from gui/themes directory) (if your port uses new GUI)
      • translations.dat (from gui/themes directory)
      • pred.dic (from dists directory)
      • access.dat (from dists/engine-data)
      • access.dat (from dists/engine-data)
      • cryomni3d.dat (from dists/engine-data)
      • drascula.dat (from dists/engine-data)
      • fonts.dat (from dists/engine-data)
      • hugo.dat (from dists/engine-data)
      • kyra.dat (from dists/engine-data)
      • lure.dat (from dists/engine-data)
      • mort.dat (from dists/engine-data)
      • neverhood.dat (from dists/engine-data)
      • queen.tbl (from dists/engine-data)
      • sky.cpt (from dists/engine-data)
      • supernova.dat (from dists/engine-data)
      • teenagent.dat (from dists/engine-data)
      • titanic.dat (from dists/engine-data)
      • tony.dat (from dists/engine-data)
      • toon.dat (from dists/engine-data)
      • ultima.dat (from dists/engine-data)
      • (from dists/engine-data)
      • xeen.ccs (from dists/engine-data)
      • your build binary
      • your build-specific README (optional)
      • ...
  • Porters need to upload binaries at some service and then send the link to the team member managing the release (this should be detailed in the email sent to porters with the links to the tarballs).
  • Update the website internally (i.e. update the version in the repository), but do not yet put these changes online.
    • Edit include/ to update the global version.
    • Create a new XML file for the new version in data/compatibility/.
    • Update data/downloads.xml.
    • Add a news item.
    • Sparkle automatic updates
      • Create a ReleaseNotes file on FRS with the changes from this release (from NEWS file).
      • Sign the macOS and Win32 binaries with our private key for Sparkle
      • Update the scummvm_appcast.xml file in scummvm/dist/macosx/.
      • Copy the app cast file on the website as appcasts/macosx/release.xml
    • Copy over the release files to FRS
      • Set the OS for the newly uploaded binaries (click on the (i) next to each binary).
        • -win32.exe as Windows binary
        • -macosx.dmg as Mac binary
        • .tar.bz2 as Linux, FreeBSD and Other binary
        • -solaris-x86.tar.gz as Solaris binary

Tagging a version

  • When 1.7.0 is ready to be announced, make a permanent v1.7.0 tag in git to mark the release
    • git checkout branch-1-7-0
    • git tag -m "Tag v1.7.0" v1.7.0
    • git push origin tag v1.7.0
  • Also increase the version number on the 1.7.x branch to 1.7.1pre
    • git checkout branch-1-7
    • devtools/ 1 7 1 pre
    • git commit -m "RELEASE: This is 1.7.1pre" -a
  • Create annotated tag desc/1.7.1pre on that commit and push
    • git tag -m "Mark 1.7.1pre" desc/1.7.1pre
    • git push origin tag desc/1.7.1pre branch-1-7:branch-1-7

Creating source tarballs

Then you need to create and upload the tarballs.

devtools/ scummvm 1.9.0
devtools/ scummvm-tools 1.9.0

Then upload the resulting scummvm-1.9.0.tar.gz, scummvm-1.9.0.tar.bz2, scummvm-1.9.0.tar.xz and to the FRS.

Signing binaries

Put tarballs into directory archives/, run:

bin/generate_appcast archives/
bin/old_dsa_scripts/sign_update archives/scummvm-2.1.1-win32.exe dsa_priv.pem
bin/old_dsa_scripts/sign_update archives/scummvm-2.1.1-macosx.dmg dsa_priv.pem

The first line will generate file archives/release.xml. The following ones will just spit out DSA signatures.

Copy/paste signatures to dists/macosx/scummvm_appcast.xml in the main git repo.

Then run:

make publish-appcast
cd ../scummvm-web
git commit -m 'WEB: Sync appcast' -a

News & Notification

Write a news blurb (or rather multiple to be used in the following). Usually, you want a bit longer one for the website, a list for Versiontracker, something with proper english sentences for Freshmeat, etc....

  • Write a news item for our website (also to be used as a template for news items on other sites).
    • Create data/compatibility/compat-2.1.1.xml
    • Update data/downloads.xml file
    • Change version constants in include/Constants.php
    • Make sure Sparkle cast is updated (see #Signing binaries)
  • Update / notify various sites:
    • Post about the release on our forums
    • Post about the release on Facebook
  • Put the updated web site online
  • Update IRC and Discord channel topics

Updating the wiki

  • Update Template:StableVersion. This is used for links to the Compatibility page for the stable version and for the latest stable version info field for each platform.
  • Move newly supported engines in the Complete engines in the latest stable version section on the Engines page.
  • Add the first release field on the info box of the newly supported engines.
  • Update Platforms page if status changed for some of the platforms (e.g. no release for the latest stable version). For these platforms the latest stable version info will also need to be changed if it was using the StableVersion template.
  • Set the First Official Version field for new platforms.
  • Update the support field on the info box of the newly supported games. Also change these games from Unsupported Games category to Supported Games category.