Software Release Checklist

Pilot checklists were developed when flight procedures became so complex that pilots started to leave out important steps. In that vein, given that there are just too many details to remember when releasing a software product, a checklist is very helpful.

In preparing to release my first product, I am going through a checklist that I found somewhere on the web. I’m not exactly sure where, and I didn’t turn it up again by Googling for certain phrases. Maybe I found it in a C4 video or a Podcast. Anyway, if anybody recognises it, or has suggestions about things I’ve missed, I’d be happy to give credit or add to the list. Here is the checklist I am working with:

Preparation

• Remove (or hide) any test menus or toolbar icons.
• Make sure help files are up to date

Compiling

• Update version numbers in info.plist: CFBundleShortVersionString for a human-readable number, CFBundleVersion for incremental build number
• Make sure code stripping is turned on in release
• Make sure correct architectures and SDKs are selected (Universal Binary)
• Make sure general project setting “Cross-Develop using Target SDK” is correct (Platform Support/Universal Binary)
• Set LSMinimumSystemVersion
• Update Credits.rtf, Software License Agreement, ReadMe

Testing

• Test languages
• Test against supported OS versions
• Test the About panel

Bundle

• Copy required files to deployment folder
• Create compressed bundle(s)

Website

• Backup website in preparation for changes
• Copy distribution build to appropriate web folder
• Update history page
• Update Sparkle Appcast information
• Update relevant screenshots, support pages, store pages
• Update sitemap.xml
• Test site locally
• Upload and test site

Notifications

• Write and submit press release (prMac.com)
• Post to: Apple Downloads, MacUpdate, I Use This, Bodega, VersionTracker