[Adium-devl] Release Plans - 1.3.4/1.4

[Peter Hosey]

I further propose that we move to DWARF-with-dSYM for our releases,  
including nightlies, alphas, and betas, starting with 1.3.4 and 1.4.

First, I'd like to split out the projects' configurations into  
xcconfig files. One key feature that they have is the ability to  
#include other xcconfig files, which means we can cut out a lot of  
repetition: Settings that we currently repeat in multiple projects, we  
could have only once in a single file.

I'm working on xcconfig-extract again with this goal in mind, but as I  
write this, I'm not sure I'll use it. It may be better to hand-write  
only a few xcconfig files and use those files in every project. An  
unmodified export of the current settings from the projects would not  
eliminate any repetition at all.

One way or another, once we have our build settings in xcconfig files,  
we can flip the DWARF-with-dSYM switch[1]. Then, we'll want to modify  
our release-build process to archive the dSYM bundles and publish each  
archive on the website. That should include nightlies as well.

Thereafter, when we get a crash report for a release we have dSYM  
bundles archived for, we'll download the appropriate archive, unzip  
it, then feed the crash log into the Symbolicator[2]. That will  
symbolicate the crash log using the dSYM bundles.

I did this on Growl last month; here are the changesets:

	http://growl.info/hg/growl-development/rev/07c18306756c
	http://growl.info/hg/growl-development/rev/cda6a8576c59
	http://growl.info/hg/growl-development/rev/3ac6e6d3547a

On the nightly page, we should include the UUIDs from Adium.app.dSYM.  
One of these will be in every Adium crash log, in the Binary Images  
section; this is the quickest way we can look up the correct dSYM- 
bundle archive for a given nightly. You can use mdls to obtain these  
UUIDs:

% mdls -name com_apple_xcode_dsym_uuids Documents/Growl\ dSYM\ bundles/ 
Growl-dSYM-1.1.5b1/GrowlHelperApp.app.dSYM
com_apple_xcode_dsym_uuids = (
     "403E7F27-35B6-0A4B-9E66-8E90A6286444",
     "D6C9FFD4-03DC-2224-B112-B3FB50559772"
)

[1]: http://developer.apple.com/tools/xcode/symbolizingcrashdumps.html
[2]: http://boredzo.org/symbolicator/