Difference between revisions of "HOWTO-Release"

From ScummVM :: Wiki
Jump to navigation Jump to search
m (→‎Binaries: Add toon.dat and hugo.dat)
Line 96: Line 96:
 
* Write a news item for our website (also to be used as template for news items on other sites).
 
* Write a news item for our website (also to be used as template for news items on other sites).
 
* Update / notify various sites:
 
* Update / notify various sites:
** Create a SF.net news item (Fingolfin, Sev, ...)
+
** Create a SF.net news item
** [http://freshmeat.net/ Freshmeat] (Fingolfin, Sev ... but anybody can do it)
+
** [http://freshmeat.net/ Freshmeat]  
** [http://www.versiontracker.com Versiontracker.com] (Fingolfin)
 
** Update [http://www.heise.de/software/ heise software directory] (Fingolfin)
 
 
** Post about the release on our forums
 
** Post about the release on our forums
 
** ... more ?
 
** ... more ?

Revision as of 08:23, 30 June 2011

How to make a ScummVM release.

This is work in progress and needs to be completed!


Preparations

  • 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

Testing

  • 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

Branching

  • Create a branch for the release, named branch-1-3-0 (TODO: Document the exact procedure)
  • Update version numbers on master (to 1.4.0git) and branch (to 1.3.0pre) (TODO: Document the exact procedure; also see below)
  • Create desc/* git tags for the new git/pre versions, by doing:
    • git tag -m "Mark 1.4.0git" desc/1.4.0git 204a9c2e
    • git push origin tag desc/1.4.0git
    • git tag -m "Mark 1.3.0pre" desc/1.3.0pre 40df14a7
    • git push origin tag desc/1.3.0pre

Preparing the source

  • You have to update the versions in all relevant files. There is a script, tools/update-version.pl 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
    • NEWS
    • COPYRIGHT
  • Review the following port specific files for version updates:
    • backends/platform/gp2x/build/README-GP2X
    • backends/platform/gp2x/build/README-GP2X.html
    • backends/platform/ps2/READ_PS2.TXT
    • backends/platform/psp/README.PSP
    • backends/platform/symbian/README
    • backends/platform/wince/README-WinCE.txt
    • backends/platform/ds/arm9/dist/readme_ds.txt
  • Make sure package descriptions are up-to-date:
    • dists/redhat/scummvm.spec
  • Create MSVC project files
    • First of all you need to build the create_msvc tool by using "make tools"
    • Run create_msvc with "../.. --msvc-version 8" from dists/msvc8
    • Run create_msvc with "../.. --msvc-version 9" from dists/msvc9
    • Run create_msvc with "../.. --msvc-version 10" from dists/msvc10
    • Add all *.vcproj, *.sln, *.vsprops, *.vcxproj, *.vcxproj.filters, *.props files to the release tag in SVN
  • Make source tarballs, post them in the SF.net FRS.
    • There is a script tools/dist-scummvm.sh, which does this automatically.
    • Make sure that porters have write access to the release folder on FRS: chmod 775 <folder>

Binaries

  • 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.
    • Here is a list of files porters should include in their release archives:
      • AUTHORS
      • COPYING
      • COPYING.BSD
      • COPYING.LGPL
      • COPYRIGHT
      • NEWS
      • README (generic ScummVM one)
      • scummmodern.zip (from gui/themes directory) (if your port uses new GUI)
      • scummclassic.zip (from gui/themes directory) (if your port uses new GUI)
      • translations.dat (from gui/themes directory)
      • pred.dic (from dists directory)
      • kyra.dat (from dists/engine-data)
      • queen.tbl (from dists/engine-data)
      • sky.cpt (from dists/engine-data)
      • lure.dat (from dists/engine-data)
      • drascula.dat (from dists/engine-data)
      • teenagent.dat (from dists/engine-data)
      • hugo.dat (from dists/engine-data)
      • toon.dat (from dists/engine-data)
      • your build binary
      • your build-specific README (optional)
      • ...
  • Porters can upload binaries via SCP or SFTP: scp FILENAME SFNET_USERNAME,scummvm@frs.sourceforge.net:/home/pfs/project/s/sc/scummvm/scummvm/X.Y.Z/
  • Update the website internally (i.e. update the version in the repository), but do not yet put these changes online.
    • Edit include/config.inc.php 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.
    • Update default platform packages on sf.net FRS

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 template for news items on other sites).
  • Update / notify various sites:
    • Create a SF.net news item
    • Freshmeat
    • Post about the release on our forums
    • ... more ?
  • Put the updated web site online

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.
  • Update the support field on the info box of the newly supported games. Also remove these games from Unsupported Games category.