Release Application

First on the development computer

1. Update project’s Info.plist with new version name, make sure to indicate if it’s a beta or not.

2. Commit all changes for project and dependent projects in Subversion. These should all be listed in the applications Other/release_dependencies.txt project file.

3. Make a new release of the application in Subversion and update the project’s CFBundleVersion number by running the tag_release.rb script from the terminal. For example ./tag_release.rb shared/Clockwork. Note it’s important to prefix the application name with the name of the svn repository where it is stored ‘shared’ in the case of Clockwork.

4. Build the new release by running the build_release.rb script from the terminal. For example ./build_release.rb shared/Clockwork 9. The result will build the Clockwork version 9 release and copy the resulting DMG file to your desktop.

Now on the webserver

1. For each new release these files in files/releases will need to be updated:

   • <ApplicationName>.plist - For example see Clockwork.plist. This file is a plist dictionary that contains the latest CFBundleVersion number for the applications main bundle. The software update plugin uses this file to check if a new update is availible. (NOTE, edit the .plist file last since that will notify people that we are ready for them to download.)
   • <ApplicationName>.dmg - For example see Clockwork.dmg. This file should always point the the latest public release of an application. This is the URL that gets sent out to download sites, so every new public (non beta) release should replace this file with the latest release.
   • <ApplicationName>-<CFBundleShortVersionString>.dmg - For example see Clockwork-1.1.dmg. Each new release should also provide a copy with a version name. These files are listed on the project page for each application so users can download old versions.

2. After updating the releases directory visit this page admin/settings/project/reload to scan the releases directory and rebuild the applications project page.

3. Next the project release notes clockwork/releasenotes must be updated. Follow the format used in Clockwork’s release notes. Find all open issues that have been fixed and mark them as closed. Add links to these closed issues to the release notes.

4. ClockworkReleaseNotes.html in the releases folder also needs to be updated. This file should only include the last few sets of changes. When the software update plugin notices a new release this is the file that it will display on the users computer so that they know what changes are in the new release.

5. IF NOT A BETA VERSION Update version numbers on front page and product page.

6. IF A BETA VERSION Update product home page “beta” sidebar section.

7. Clear website caches.

Now on the web

All releases

• http://www.macupdate.com
• http://www.versiontracker.com
• http://osx.iusethis.com/

Big Releases

• http://www.macupdate.com
• http://www.versiontracker.com
• http://www.tuaw.com/tips/
• http://www.apple.com/downloads/macosx/submit/
• releases(a)tidbits.com
• press_releases(a)mactech.com
• press(a)macnn.com
• pr(a)macobserver.com
• pr2003(a)macintouch.com
• news(a)macminute.com
• http://www.macworld.com/info/contact/
• plugs(a)macaddict.com
• tim(a)surf-bits.com (see email from him, interested in review licenses)
• http://www.macaddict.com/magazine/disc/
• http://www.macformat.co.uk/?entry=contact_us