Move missing accessibility API declarations to OakAppKit.h
Add OakSetAccessibilityLabel function

This function makes it easy to set accessibility "labels" for UI elements.
It is flexible - takes care of NSView vs. NSControl case, labels can be
specified directly as a string or as a user interface element.
Add ability to specify AX labels in UI functions

Accessibility labels now can be specified conveniently as a parameter
of a UI construction function.
Add accessibility labels to Find dialog
Use UI creation functions for accessibility in status bar
Add my work email as contributor address
Post find feedback accessibility announcements
Notify VoiceOver user of find window status bar changes

We don’t have a specific element associated with the result being announced so we use the current responder (unless it has accessibility ignored, in which case we do not post any notification).

Using the current responder is not ideal, but I do not know how we can either associate the notification with the find panel or post it as a global notification.
Do not stack allocate potentially large buffer

Also test that each system function used actually succeeds.
Increase the number of tests for sanitizing UTF-8

Also harmonize the formatting of the existing tests.
Tighter code for removing malformed UTF-8 sequences
Don’t use -KU with ruby as it logs a warning with ruby 2.0
Sanitize output from TextMate.system()

Since the API specifies an NSString we must expect valid UTF-8.
Update HTML tool tips (font and WebView cache/plug-in settings)
Disable WebView plug-ins and page cache for about window
We shouldn’t (potentially) call fprintf() after vfork()

Since it was only incase of failing to close a file descriptor, it shouldn’t have played any role in practice.
Keep dispatch group around as we may call wait after process exit
Exception handler was overwriting crash report info
Add application category for OS X

Applications is often not subfoldered and View --> Arrange by Application Category helps but apps need to have this metadata otherwise they're sorted into "Other" at the bottom.  https://developer.apple.com/library/Mac/releasenotes/General/SubmittingToMacAppStore/#//apple_ref/doc/uid/TP40010572-CH16-SW8  (this applies to all Mac apps, not just those coming from App Store)
When updating bundles we rename old bundle before delete

This means if TextMate is terminated during update, worst-case is that the bundle is gone (which we can detect) rather than potentially leaving a partially deleted bundle on disk.

Also, since we now move in the updated version immediately after removing the old, the time where the disk is in a bad state (compared to our bundle index) has been minimized.