Version 51 (modified by leper, 9 years ago) ( diff )

Update for r16906/#3359.

Standard schedule

  1. Day 0: Feature freeze
  2. Day 3: String freeze
  3. Day 6: Translation freeze
  4. Day 6: Commit freeze
  5. Day 7: Packaging
  6. Day 9: Release

Release progress table

Put your name into the "Accepted by" column to take over a task and agree to completed it in time according to the Deadline. Update the status column regularly enough to keep team member informed. Especially note if you are waiting for input or are otherwise prevented from working on the task.

Next release: Alpha 18 Rhododactylos
Current phase: Commit freeze/Packaging

Development

Deadline: February 8th

Task Accepted by Status
Start release process Team Done
Announce string freeze leper Done

Feature freeze

Deadline: Sunday, February 8th

Task Accepted by Status
Organize staff match (testing)

String freeze

Deadline: Wednesday, February 11th

Task Accepted by Status

Translation freeze

Deadline: Saturday, February 14th Sunday, March 1st

Task Accepted by Status
Confirm translation freeze leper Done
Translation check leper Mostly done (ran the script)

Packaging

Deadline: Tuesday, March 3rd (can start after latest translations are committed)

Task Accepted by Status
Prepare for packaging Team Done
Packaging: Windows and Linux Philip Done
Packaging: Mac OS X historicbruno Done
Package testing: Linux
Package testing: Windows
Package testing: Mac OS X historicbruno, Team
Upload to Sourceforge Philip Done

Release

Deadline: Friday, March 13th

Task Accepted by Status
Write release announcement Jeru Mostly done
Create release video Brynn Done
Download redirects Philip Done
Notify packagers leper Done
Publish announcement
Prepare lobby leper prepared (new bot and lobby set up)

Task descriptions

Start release process

Description:
The team decides that there are enough new features and that it's time to release a new alpha version. Usually in a team meeting, we decide when the regular schedule starts and if there are any differences to the predefined schedule.
Can be completed in phase: Development
Candidates: Whole team (usually at the meeting)

Announce string freeze

Description:
Translators should be informed about the planned String freeze date and the Translation freeze date. The idea is to give them some time to polish the final translations for the release. During development, they probably don't always update translation within a few days after something has changed. Also upload updated .pot files and make sure you update them if original strings change or get added in the next days.
Can be completed in phase: Development
Candidates: Gallaecio, Leper, Sanderd17, Yves, Itms

Organize staff match (testing)

Description:
If possible a staff match should be organized before the release. Often important bugs get discovered in such staff matches. Organizing the match means finding a good date and time and informing the other team members (or community members).
Can be completed in phase: Development
Candidates: Whole team

Confirm translation freeze

Description:
You make another announcement on the translation platform at the specified and announced Translation freeze date (assuming it hasn't changed in the meantime). After that, you regenerate the translation templates via updateTemplates.py and the translations (for backup purposes) via pullTranslations.py.
Can be completed in phase: Translation freeze
Candidates: Gallaecio, Leper, Sanderd17, Yves, Itms

Translation check

Description:
Check the translations for "vandalism". It's really just checking if there are any strings that were added in bad intent and not about trying to improve translation quality. There's a script to check the translation files for URLs (TODO: where?), but this task also involves manual checking. Obviously we can't carefully read through all strings in all translations.
Can be completed in phase: Translation freeze
Candidates: Whole team

Multiplayer lobby adjustments

Description

  • Maybe reset SVN (current alpha) rankings.
  • Change the bot's welcome message to notify users that a new version is available.
  • Create a new MUC room and add a new bot for the SVN version.


Can be completed in phase: Release
Candidates: Leper, Josh, Scythetwirler

Prepare for packaging

Description


Can be completed in phase: ???
Candidates: Whole team

Setup packaging

Description
These are common tasks that need to be done for all packaging on all systems.

  • Update public trunk checkout
  • Ensure it is clean (svn st --no-ignore)


Can be completed in phase: Packaging
Candidates: People doing packaging

Packaging: Windows and Linux

Description


Can be completed in phase: Packaging
Candidates: Whole team

Packaging: Mac OS X

Description

  • Complete the steps in Setup packaging
  • Build OS X app bundle:
    • Requires OS X and Xcode
    • Read documentation in build-osx-bundle.sh, update options if necessary (defaults work with Xcode 4.2+ and Lion)
    • Run build-osx-bundle.sh --release, by default it creates a 64-bit 10.7+ compatible bundle, ~/0ad-export/0ad.app
    • Package app into DMG (as outlined here and here)
      • Use Disk Utility to create an uncompressed DMG large enough to hold 0ad.app
      • Set background image, build/resources/dmgbackground.png
      • Copy 0ad.app and Applications shortcut, arrange icons, set folder view options as desired
      • Create a bzip2-compressed DMG with hdiutil: hdiutil convert 0ad.dmg -format UDBZ -o 0ad-[version]-alpha-osx64
  • Upload releases to http://releases.wildfiregames.com/
  • Verify sha1sums on server


Can be completed in phase: Packaging
Candidates: Historicbruno, Wraitii

Package testing: Linux

Description

  • Delete ~/.cache/0ad
  • Extract release
  • Build with config=debug, run test_dbg, run game, run editor
  • Build with config=release, run test, run game, run editor


Can be completed in phase: Packaging
Candidates: Whole team

Package testing: Mac OS X

Description

  • Delete ~/Library/Caches/0ad/
  • Mount release DMG
  • Run 0ad and test that it works on e.g. Snow Leopard and Lion
  • Test Atlas (main menu > Tools & Options > Scenario Editor)
  • Delete ~/Library/Caches/0ad/


Can be completed in phase: Packaging
Candidates: Whole team

Package testing: Windows

Description

  • Delete %localappdata%\0ad\cache
  • Extract release
  • Run pyrogenesis.exe, check everything seems to work
  • Run Atlas.bat, check everything seems to work
  • Delete %localappdata%\0ad\cache
  • Build Debug version, check everything seems to work
  • Run test project


Can be completed in phase: Packaging
Candidates: Whole team

Upload to Sourceforge

After all packages are created and tested, they can be uploaded to sourceforge.

rsync -v --progress -e ssh 0ad-${SVNREV}-*.{exe,gz,xz} philiptaylor,zero-ad@frs.sourceforge.net:/home/frs/project/z/ze/zero-ad/releases/


Can be completed in phase: Packaging
Candidates: Philip

Write release announcement

Description

  • Write a release announcement that will be published on the website and other places like Moddb.
  • Describe new features, content and major bugfixes. If necessary ask people to provide descriptions.
  • Create one or more unique screenshots that fit well for this Alpha release (or find someone to create these).
  • Write a short description of the Alpha name and the reasons why we have chosen this name (historical term around the timeframe of 0 A.D.).


Can be completed in phase: Feature freeze
Candidates: Jeru

Create release video

Description
An Alpha release video showcases the new features, content and major bugfixes of this version. It focuses more on the features that can be shown well in a video. Remember to upload the video on the play0ad youtube channel.
Can be completed in phase: Feature freeze
Candidates: Brynn

Release: Download redirects

Description

  • Update release redirects to point to SF
  • Update Linux release page (links, file sizes, checksums?):


Can be completed in phase: Release
Candidates: Philip, ...?

Release: Notify packagers

Description


Can be completed in phase: Release
Candidates: Leper, Everyone

Release: Publish announcement

Description


Can be completed in phase: Release
Candidates: Feneur, Jeru, Leper

Update release progress on Trac

Description:
Remove all content from the Release progress table and replace "Next release" with the right version number.
Can be completed in phase: Development
Candidates: Everyone

Note: See TracWiki for help on using the wiki.