wiki:Developer/ReleaseChecklist
Last modified 2 years ago

Release Checklist

Table of Contents

  1. Release Checklist
  2. All Platforms
      1. Build Notes
  3. Windows
  4. Unix
  5. OS X
  6. Documentation
  7. Website
  8. FTP
  9. Trac
  10. Translations
    1. Unix/MAC
  11. Dictionaries
    1. Language Specific Info

There are many steps required before a release is made. This page should collect all the enumerated steps required for each platform in order to complete an official release.

All Platforms

  1. Edit VersionNumber with correct trunk/aegisub/src/version.cpp
  2. Collect latest versions of dictionary and thesaurus files.
  3. Build each platform using a non debug build and make sure it runs correctly, test various common operations.

Build Notes

  1. FINAL_RELEASE must be set when building.

Windows

  1. Update trunk/aegisub/packages/win_installer/aegisub2.iss with version info and new dist-files.
  2. Build installer.
  3. Test installer in a fresh installation of Windows XP SP3, Windows Vista SP1 32 and 64 bit. Make sure all features work and no runtime libraries are missing, and all files installed are up to date.
  4. Test uninstallation.
  5. Test installing previous version, then upgrading with new version.
  6. Test installer behaviour when running as a standard user.

Unix

  1. Set aegisub_version_(major|minor|revision) in trunk/aegisub/src/configure.in.

OS X

  1. Ensure these are added to the bundle:
    • Dictionaries
    • Thesaurus
    • Updated std-wx translations.
    • Resource files (anything in docs/)
  2. Open the DMG and be sure the correct version is listed.
  3. Check DMG image + text alignment and ensure it auto-opens when mounted.
  4. Check trunk/aegisub/packages/osx_bundle/Contents/Info.plist
    • CFBundleLocalizations matches po/LINGUAS

Documentation

Website

FTP

  1. Old releases need to be moved from pub/releases to pub/archives.

Trac

  1. Set complete date on appropriate milestone.
  2. Add a new version with the release date set to the complete date of the milestone.
  3. Set next milestone as the default for new tickets.
  4. Update the version in Bugs to the latest version.
  5. Edit trac_post_commit.py and modify the mstone dict with the correct paths/milestones.

Translations

  1. Ensure all wxstd.mo files are up-to-date for the WX version we're releasing. See  http://wxwidgets.org/about/i18n.php
  2. Re-generate XX.mo from the .po files to ensure they're all up-to-date.

Unix/MAC

  1. Make sure po/LINGUAS lists all the languages we're releasing with
  2. Update the static list in browser:trunk/aegisub/src/aegisublocale.cpp

Dictionaries

  1. Make sure we have one dictionary for EACH of the translations we ship with.
    • This includes both spelling and thesaurus.

There are two sites that should be checked against for dictionary inclusion:

Language Specific Info