With Github's help, we've added Pivotal Tracker to the list of Github's built in service hooks, making it easier to tie commits to Tracker stories.
To set it up, go to the Repository Administration section of your Githup repo, click on Service Hooks on the left, and choose PivotalTracker from the list. Enter your API token, and you should be good to go.
More on Tracker commit hooks on the API help page.
A frequent feature request for Pivotal Tracker is support for parallel tracks of development for multiple pairs of developers (you are pair programming, right?) It's true that Tracker does not fully support parallel tracks within the same Project, but you can get most of the way there by doing what we do on many Pivotal Labs projects: use labels to identify multiple tracks of development. With labels, you can easily visualize and manage parallel development tracks while keeping your team's work in one Pivotal Tracker Project.
Whether you're using Cedar or not, if you've upgraded to the iOS 4.0 SDK you may have run into some odd behavior with exception handling blocks not catching exceptions. Strangely, the problem isn't due to the exceptions themselves (at least not in any obvious way), but with how you call functions that raise exceptions. An exception thrown from within a method you invoke directly will function as expected. However, if you invoke that same function indirectly using NSInvocation any exception thrown becomes uncatchable, crashing the current process regardless of any exception handling code.
This happens only when running against the currently available iOS 4.0 SDK. Exception handling for both direct and indirect invocations performs as expected when using the OS X 10.6 SDK and previous versions of the iPhone SDK.
Though I am certain someone could do it, it is hard to dispute the connection between having choices and control over your daily work and overall job satisfaction. The people with more power to govern themselves will typically report that they are more satisfied with their jobs. This is why pairing can play a huge part both with picking who you work with and what you work on.
Help
- Does anyone know how to set a caching header for urls that end with a cachebusting string (e.g. ?123456789)? Apparently you're not allowed to get the query string when mucking with rewrite rules. A couple of people think that you are able to get your hands on it...somehow.
- How do you do a screen capture from the Mac command line? We want to do a screen capture of a running emulator. Maybe something like this?
Interesting Things
Rails 2.3.8 - for nested attributes, '_destroy' is the new '_delete'. Looks like the Rails team is on top of it. Use
@foo.update_attributes(:foo_attributes => {'0' => {:id => '1', '_destroy' => '1'}})instead of
@foo.update_attributes(:foo_attributes => {'0' => {:id => '1', '_delete' => '1'}})