Release Notes

We’re big fans of Beanstalk. In fact we like them so much we now host all of our production repositories there.

Beanstalk offers top-notch cloud-based version control with great deployment, integration and collaboration features. It also has one of the best user interfaces.

And that got us thinking: if we could integrate one of the leading repository-hosting platforms with the ultimate Subversion client, Mac users around the world would be in for a treat.

So that’s what we did.

The integration makes it super-easy to start using Beanstalk’s Subversion hosting with Cornerstone. If you already have a Beanstalk account just copy the URL from your repository’s info page and Cornerstone will automatically add the information it needs. All you need to do is provide your account details and you’re done.

To celebrate the new partnership, all Beanstalk account holders receive a 10% discount coupon for Cornerstone. Just log into Beanstalk and either create a new repository or visit the repository help page to get your discount code for use in the Cornerstone web store.

2.7 is a free upgrade for all Cornerstone 2 license holders running Mac OS X 10.6 and 10.7. Please note that 2.7 does not run on Mac OS X 10.5 Leopard.

New Features

1. Compatibility with Subversion 1.7

   Cornerstone 2.7 adds full support for Subversion 1.7, including the ability to connect to 1.7 servers and access 1.7-format repositories.

   2.7 also provides the ability to upgrade a 1.4-, 1.5- or 1.6-format working copy to the new 1.7 format. However, it is not possible to downgrade a 1.7-format working copy (as is the case with older working copies.)

2. Beanstalk Added as a Cloud Service Repository Type

   Zennaware has partnered with Wildbit to integrate support for their Beanstalk Subversion hosting service into Cornerstone. The Add Repository window’s new Beanstalk cloud service greatly simplifies connecting to a Beanstalk-hosted repository.

   The Beanstalk page also provides a Sign Up for a Repository button which enables a user to quickly and easily sign up for a free or trial hosting plan with Beanstalk.

   Beanstalk repositories are displayed in the source list using a specific icon enabling easy differentiation from generic http/https/svn/svn+ssh/file repositories.

3. Improved Support for Certificate-Based Authentication

   Version 2.6 and earlier provided limited support for certificate-based authentication with SSL/TLS servers. This support was substantially improved for Cornerstone 2.7.

   Subversion is traditionally configured to use PKCS#12 certificate files stored at a location in the file system of the user’s choosing. Earlier versions of Cornerstone respected these settings but would not prompt the user for a certificate file or a password if necessary.

   These shortcomings were rectified for 2.7.

   Cornerstone now provides full support for using certificates (and their associated private keys) stored in the Mac OS X keychain. This improves on Subversion’s traditional file-based certificate configuration in a number of ways by providing simpler configuration and greater security.

   Cornerstone 2.7 can be configured (using the new Certificates preference pane) to reference one or more certificates stored in the keychain. Cornerstone can also import PKCS#12 files into the keychain.

   If multiple certificates are configured then Cornerstone will ask for the preferred certificate with the same standard user interface used by Safari and other SSL-aware applications.

   See the Configuring Certificate-Based Authentication article in the Cornerstone help book (Help > Cornerstone Help) for more information.

4. Improved Handling of Invalid SSL Server Certificates

   Cornerstone now uses the standard system-provided user interface for asking the user to accept an untrusted server certificate. Certificates accepted permanently by the user are added to the user’s keychain in the same manner as Safari and other SSL-aware applications.

Performance Improvements

1. HTTP Performance

   Subversion 1.7 introduces a new HTTP-based protocol that promises improved network performance. 1.7-capable client applications such as Cornerstone will automatically use the newer protocol when connecting to a 1.7 server.

   Subversion supports the use of two different client libraries for accessing repositories using the HTTP protocol: Neon and Serf. While the Subversion developers have added support for the newer 1.7 protocol to both these libraries, client applications must use the Serf library to see the maximum performance gains (although Neon users should also see significant performance improvements).

   For maximum compatibility, Cornerstone has traditionally used the Neon HTTP library (the Serf library is missing support for certain HTTP features), and this continues to be the case in 2.7. As a result Cornerstone users will not gain the full performance benefits of the 1.7 HTTP protocol.

2. Log View Filtering Performance

   The time taken to render the contents of the log view after changing the selected filter was reduced by up to 60%, resulting in a significantly more responsive user interface.

Usability Improvements

1. Improved SSH Handling

   Cornerstone’s SSH password prompt handling was improved. This is relevant for working copies checked out using svn+ssh:// that did not include the user’s account name (in the form svn+ssh://user@example.com/repos) in the repository URL.

   In previous versions, Cornerstone would specify the server name (e.g. example.com) as the location when prompting for a password. This was misleading as the user account for which the password was required was not indicated.

   Cornerstone 2.7 now correctly displays the user account that SSH is requesting the password for.

2. Improved Handling of Temporary Credentials

   The way in which Cornerstone manages credentials (usernames, passwords, certificates etc.) was re-written for 2.7. During this process care was taken to enable the user to use Cornerstone without permanently storing their credentials in the keychain or on disk.

   Previous versions of Cornerstone could re-prompt for credentials under certain circumstances. 2.7 improves this behavior by prompting a maximum of once for each working copy or repository in the source list.

3. Multiple Folders are Created as a Single Revision

   In Cornerstone 2.6 and earlier, creating a path of folders (or a folder with “branches”, “tags” and “trunk” sub-folders) in the repository browser resulted in multiple revisions: one for each folder created.

   Cornerstone 2.7 improves on this behavior by creating all folders in a single revision.

Behavioral Changes

1. Certificates Specified in Subversion’s Config Files are Ignored

   Cornerstone 2.7 can only use certificates stored in the keychain. Support for the traditional method of configuring Subversion to use a PKCS#12 file was intentionally removed.

   If you have been using certificate-based authentication in the past then you will need to configure Cornerstone 2.7 to reference the certificate in the keychain.

2. Background Status Checks Fail for Servers with Untrusted Certificates

   Cornerstone no longer automatically accepts untrusted server certificates when performing background status checks to determine repository status displayed in the working copy source list.

   Instead, Cornerstone 2.7 will reject untrusted certificates until accepted by the user as part of an interactive operation.

3. Files Dragged from Finder are Now Copied

   Prior to Cornerstone 2.7, dragging an unversioned file from Finder to a working copy initiated a move operation. This behavior was changed for 2.7 and files are now copied instead.

4. Folder Paths Can’t be Created in 1.4-Format Working Copies

   Cornerstone allows a path of folders to be created by specifying multiple path components in the New Folder window. E.g., specifying “Libraries/Core/JSON” will create “Libraries”, “Core” and “JSON” if they don’t exist.

   Cornerstone 2.7 improves on the existing functionality by combining the creation of all folders into a single revision when performed directly against a repository (there is no difference in behavior for working copies). This improvement was implemented by switching to a newer Subversion API that is only available in 1.5 and above. A side-effect of this change is that creating a path of folders is no longer supported for 1.4-format working copies. Attempting to create a path of folders will result in an error if any of the parent folders do not already exist.

   Cornerstone users with 1.4-format working copies can work around this limitation by:

   • creating each required folder with a separate use of the New Folder command, or
   • upgrading the working copy to 1.5 format or newer.

Compatibility

Cornerstone is compatible with Mac OS X 10.6 Snow Leopard and 10.7 Lion. Note that 2.7 is not compatible with Mac OS X 10.5 Leopard.

Cornerstone 2.7 is fully backwards-compatible with 1.5 and 2.6. All configuration and settings are transparently migrated to version 2.7 when the new version is run for the first time.

It is important to note, however, that Cornerstone 2.6 and older will not be able to access 1.7-format working copies created by Cornerstone 2.7.

Cornerstone’s configuration files are forward-compatible with 1.5, i.e. you can run versions 1.5, 2.0, 2.1, 2.2, 2.5, 2.6 and 2.7 against the same configuration databases in your Application Support/Cornerstone folder.

Resolved Issues

• Use OS-provided certificate viewer with untrusted server SSL certificates. (#138)
• Dropping files from Finder onto working copy should always copy files. (#626)
• Support client side certificate-based authentication. (#703)
• Cornerstone should prompt for SSL client certificate if not configured in .subversion/servers. (#909)
• Cornerstone should use the root certificates located in the Keychain to validate SSL certificates which are not validated by OpenSSL by default. (#926)
• Enhance SSL certificate support by adding a Keychain provider to Cornerstone. (#1002)
• Provide support for SSL certificates that update frequently. (#1083)
• Cornerstone displays an error when attempting to undelete a file located in the root of a working copy. (#1217)
• Cornerstone displays an error when attempting to copy a file from a working copy to a repository, or vice versa. (#1218)
• The “secure connection” icon is displayed incorrectly when in full screen mode. (#1221)
• It should be possible to replace a file in a working copy using a drag and drop move operation. (#1223)
• Compare view can display incorrect log message in annotation (i.e. blame) popup window for lines originating from revision in which the file was first added. (#1231)
• Switch options window should record the source URL when switching such that it is available in the URL field popup menu when switching back. (#1232)
• .prej files are displayed for working copy files with both text and property conflicts. (#1236)
• Cornerstone displays an error when a space character is entered into the server name field in the “Add Repository” window. (#1237)
• Creating a repository folder with “trunk”, “branches” and “tags” subfolders should be done in a single revision. (#1238)
• The repository source list’s resize cursor is visible even if the repository source list is hidden. (#1239)
• Cornerstone doesn’t support version 1.1.6 of the compare tool Kaleidoscope. (#1240)
• Typographic (i.e. “curly”, or “smart”) quotation marks should be used instead of neutral (i.e. “straight”) quotation marks when displaying filenames in text. (#1241)
• Working copy browser displays a depth of “Folder Only” for unversioned files. (#1242)
• The display of a modal window during repository setup could result in the repository being added to the source list even if the connection failed. (#1244)
• External folders located in more than one level of nested unversioned folders are not displayed in the correct location in the working copy browser. (#1245)
• Replaced references to “Made by Sofa Kaleidoscope” with “Black Pixel Kaleidoscope” in help book.
• Certificates preference pane should display an alert when selected certificate file cannot be read. (#1246)
• Repository browser stops refreshing automatically after the repository’s settings have been edited. (#1247)
• The log view does not always display the expected revision range when a revision other than HEAD is displayed in the browser view. (#1248)
• Refreshing the log view didn’t always pick up the latest revisions for the selected file or folder. (#1249)
• Log item summary contains a hanging mid-dot character for revisions committed anonymously. (#1250)
• Cornerstone’s UI blocks while the repository is contacted when refreshing the log view for a file. (#1251)
• Items modified in the repository are also marked as modified locally in the working copy browser when “Show Repository Status” is enabled (Subversion 1.7 only). (#1252)
• Cornerstone crashes when removing a repository from the source list when blame is displayed for a file in the compare view. (#1254)
• Cornerstone displays an error when committing with an external folder selected which has property modifications. (#1255)
• Relocating a working copy results in the repository URL being updated even when the relocate itself fails. (#1256)
• Cornerstone fails to connect to initially connect to a newly-created file repository. (#1257)
• Cornerstone crashes when removing a repository after displaying the repository’s log. (#1258)

In October we wrote about our plans to add support for Subversion 1.7 to Cornerstone 2.7. It was our hope that this would be ready by the end of 2011.

Unfortunately this won’t be the case.

We knew that supporting 1.7 would take more work than previous versions. We described it as “disruptive” but we didn’t anticipate just how disruptive it would be.

The Problem: Incompatible APIs, Performance Regression and SQLite

Subversion 1.7 includes a complete re-write of the code that manages working copies. While the Subversion developers have attempted to hide the differences between the old and new implementations they were unfortunately unable to do so with 100% compatibility.

For example, 1.7’s re-implementation of the working copy status API used by Cornerstone is now 10x slower than the same API in Subversion 1.6. It provides the same output, but what previously completed in 200 ms now take over 2 seconds. We don’t think this kind of performance degredation is acceptable and spent some time migrating Cornerstone to use newer and faster APIs.

But the most disruptive change results from Subversion’s use of SQLite.

Cornerstone makes heavy use of threading – almost all interactions with Subversion take place on background threads to prevent the user interface from blocking – and SQLite places strict constraints on how it’s data structures can (or, more accurately can’t) be shared between threads. As a result, certain data structures that could be shared between threads prior to 1.7 (and had worked absolutely fine in 1.3, 1.4, 1.5 and 1.6) now raise errors as soon as they’re accessed from different threads.

The Solution: Building a Platform for Future Development

We came to the conclusion that we would have to re-think certain core aspects of how Cornerstone interacts with Subversion. The constraints introduced by SQLite make it substantially more complicated to use Subversion’s APIs from multiple threads. We ended up having to re-design the way in which key data structures are allocated and managed by Cornerstone.

This has taken a lot of work. We’ve been working on this at full-tilt for the last four months, dedicating all available resources to re-building key areas of the application to serve as a solid foundation for future development.

We’ve also totally re-written Cornerstone’s security stack to enable this new design, and have done so in a way that enables key improvements such as support for certificate-based authentication and temporary (i.e. non-persistent) credentials.

Finally, we’ve also re-thought how Cornerstone should store its credentials and have replaced key areas of the Subversion authentication stack with alternatives that use the Mac OS X keychain.

These are big and worthwhile improvements. And rather than take shortcuts or rush these changes, we’ll be taking the time to get them right.

We now plan to release Cornerstone 2.7 before the end of February 2012.

Thanks for your patience.

Yesterday the Apache project released Subversion 1.7, a major update to our favorite version control system. This new version brings with it some much-requested improvements that will affect the lives of Cornerstone users in a positive way.

The most significant improvements in 1.7 are:

• Improved Working Copy Metadata Storage

  All versions of Subversion prior to 1.7 have stored housekeeping information about a working copy’s contents in hidden .svn folders distributed throughout the working copy. While not normally visible, these pesky folders have nonetheless been the cause of issues for users. In particular, moving or removing .svn folders (or the folders that contain them) with Finder or Terminal could result in Subversion (and Cornerstone by extension) no longer being able to access that working copy.

  While tools such as Finder and Terminal should still not be used to move and rename working copy items (you should always use Cornerstone or another Subversion app to do so), Subversion should be able to better handle such situations.

  So where did the data in the .svn folders go? It’s still there, but it’s now stored in a single hidden .svn folder at the top of your working copy.

  But what about performance?

  The Subversion developers claim that the new storage format should significantly improve performance. However, our own experience doesn’t support this. If anything, our testing shows 1.7 to be slower than 1.6, with real-world working copies being between 30% and 100% slower than 1.6.

  The bottom line? While the new metadata format in 1.7 should simplify working copy management – and make it more robust – it won’t necessarily be any faster.

• Improved HTTP Performance

  To be honest, Subversion’s HTTP network performance has always been, ahem, less than stellar, particularly on high-latency networks. If you use a hosted Subversion repository on the other side of the planet, then you’ll be accustomed to 3+ second roundtrip times for even the simplest actions, such as listing the contents of a repository folder or comparing a working copy against the repository. And heavyweight actions such as commits and updates can take much longer.

  This poor performance stems from Subversion’s support for the WebDav DeltaV specification. DeltaV’s failure to gain any significant traction meant that the promised inter-operability benefits were never realized, leaving only the overhead of a chatty, complex and inefficient protocol.

  1.7 implements a new, simplified HTTP protocol, which promises to reduce the time it takes to perform most common actions. The catch? You’ll need to upgrade your server to 1.7 so that it can speak this new protocol.

If you are interested in finding out more about Subversion 1.7 then we recommend that you take a look at the Subversion 1.7 release notes.

When Will Cornerstone Support 1.7?

We will roll out full support for 1.7 with the release of Cornerstone 2.7, which we plan to release before the end of 2011.

We have been working with 1.7 for quite some time. While 1.7 is not a particularly significant release in terms of end-user features, it is a disruptive release for Cornerstone. Re-writing – re-architecting even – certain aspects of the application to incorporate Subversion 1.7 is going to take some time, but we believe it will be worth the wait.

What About Cornerstone 1.5?

Active development of Cornerstone 1.x ceased with the release of 1.5 in September 2009, over two years ago.

Much water has flowed under the bridge since then, with over 4,000 changes committed to Cornerstone during the development of 2.0 and the subsequent releases of 2.1, 2.2, 2.5 and 2.6. Cornerstone 2 has diverged so far from 1.5 that it’s impossible for us to target both versions simultaneously with the integration of 1.7.

Therefore we will not be adding 1.7 support to Cornerstone 1, instead concentrating our efforts on getting 1.7 support into the hands of Cornerstone 2 users as soon as possible.

If you are still using Cornerstone 1.x and want to enjoy the benefits of Subversion 1.7 support then you will need to upgrade to Cornerstone 2.

2.6 is a free upgrade for all Cornerstone 2 license holders running Mac OS X 10.6 and 10.7. Please note that 2.6 does not run on Mac OS X 10.5 Leopard.

New Features

1. External Merge Tools Can be Used to Resolve Conflicts in Text Files

   Apple FileMerge, Araxis Merge, Deltopia DeltaWalker, SourceGear DiffMerge and Perforce P4Merge can be used to edit and resolve conflicts in text files. Cornerstone will default to using Apple FileMerge, but the user can choose their preferred tool from the Cornerstone preferences in much the same way as was already possible for external compare tools.

   When resolving conflicts using an external tool, My Changes (i.e. .mine) is treated as the original file (normally displayed on the left) and Latest in Repository (i.e. HEAD) is treated as the modified file (displayed on the right).

   The Last Update file (i.e. BASE) is treated as the common ancestor (displayed between or below the other files) and the results of the merge are saved to the working version.

2. Full Screen Mode is Supported on 10.7 Lion

   Cornerstone’s main window now supports full screen mode when running on 10.7 Lion.

   A new Enter Full Screen item was added to View menu (key equivalent Cmd+Ctrl+F). The command, which is disabled on 10.6 Snow Leopard, toggles to Exit Full Screen when the main window is in full screen mode.

3. Full Support Added for File Externals

   Cornerstone has always supported working copies with svn:external folders, and Cornerstone 1.5 improved this support with the addition of the externals editor.

   Cornerstone 2.6 builds on this foundation by adding support for file externals, specifically:

   • The correct status is displayed for file externals in the working copy browser and inspector.
   • A number of issues were fixed that prevented external files from being compared correctly.
   • The externals editor now allows files to be selected from the open panel displayed for the Check out from field (but only from the same repository as the that from which the declaring folder originated).

Performance Improvements

1. Committing Folders Containing a Large Number of Added Files is Now Significantly Faster

   In previous versions of Cornerstone, committing a large number of added files (e.g. 1,000) resulted in a long pause before the commit view was displayed.

   This has been rectified in Cornerstone 2.6.

2. Working Copy Refresh Performance was Improved

   The performance of working copy status checks performed whenever Cornerstone performs or detects a change in a working copy was improved by about 20%.

   This may not be noticeable on newer Macs but should be significant on Macs with slower processors.

Usability Improvements

1. Unversioned items can now be committed when selected

   Previously, the commit command was disabled when an unversioned item was selected. This is no longer the case.

2. Name field was added to the Repository Status section of the Inspector

   A new Name field was added to the Repository Status section of the Inspector displayed for working copy items. This displays the name of the selected item in the repository, which may differ from the name of the item on the local file system.

3. Added Copy URL menu alternate to source list’s working copy menu

   Holding down the Option key when the source list’s working copy context menu is displayed causes the Copy Path menu item to be replaced by Copy URL.

   This command can be used to copy the complete URL for the working copy to the clipboard for pasting to another application.

Compatibility

Cornerstone is compatible with Mac OS X 10.6 Snow Leopard and 10.7 Lion. Note that 2.6 is not compatible with Mac OS X 10.5 Leopard.

Cornerstone 2.6 is fully backwards-compatible with 1.5 and 2.5. All configuration and settings are transparently migrated to version 2.6 when the new version is run for the first time.

The Cornerstone 2 configuration databases are forward-compatible with 1.5, i.e. you can run versions 1.5, 2.0, 2.1, 2.2, 2.5 and 2.6 against the same configuration databases in your Application Support/Cornerstone folder.

Resolved Issues

• It should be possible to open conflicted files in FileMerge to perform a 3-way merge for conflict resolution. (#948)
• Cornerstone crashes due to a Subversion assert when a server name containing upper case characters is entered in the “Add Repository” window. (#983)
• Cornerstone’s main window should support full screen mode on 10.7 Lion. (#1183)
• Information inspector pane incorrectly displays a gutter for the vertical scroller when running on 10.7 Lion. (#1189)
• Cornerstone is very slow to display the commit view when the selected change set contains a large number of unversioned files. (#1191)
• The Commit command is disabled when an unversioned file is selected, even if the “Before committing…” preference is set to automatically add unversioned files to the working copy. (#1194)
• Cornerstone’s externals functionality should be improved to provide full support for individual file externals. (#1195)
• Renaming or moving an external folder results in an error. The rename and move commands should be disabled for external folders. (#1197)
• An error is displayed when right-clicking a repository item displayed in the working copy browser that doesn’t exist locally when “Show Repository Status” is enabled. (#1200)
• The original name of a working copy item in the repository should be visible in the Inspector. (#1209)
• Layout of the Lock window is irreversibly broken when the window is reduced to a small size. (#1211)
• Attempting to overwrite a folder under version control (e.g. by dragging a folder onto Cornerstone from Finder) results in an overwrite prompt being repeatedly displayed. (#1212)
• Pasting file:/// into the Add Repository sheet results in the path popup field displaying “Macintosh HD – (null)” (#1213)

2.5.2 is a maintenance release which solves issues uncovered since the release of 2.5.

See Release Notes for 2.5 for more information on the new features and improvements introduced with 2.5.

Resolved Issues

• Issue tracking numbers are not formatted as URLs in history view for working copy files checked out using a URL that differs from the repository used to define the number rules. (#640)
• It should be possible to define user properties that include “svn” in the prefix e.g. tsvn:autoprops. (#1192)
• Open panel exhibits visual artifacts in the lower corners on Mac OS X 10.7 Lion. (#1198)
• Revision numbers are parsed incorrectly on Macs configured to use commas as decimal point separators (e.g. in Germany) (#1201)
• Revision numbers are not formatted using the thousand separator as specified by the user’s “Language and Text” system preferences (#1206)

2.5.1 is a maintenance release which solves issues uncovered since the release of 2.5.

See Release Notes for 2.5 for more information on the new features and improvements introduced with 2.5.

Resolved Issues

We are excited to announce that we will be discounting Cornerstone 2 from the standard price of $59 to just $39 in August. The offer will be valid from August 1st to August 31st.

Please note that the following restrictions apply:

• Full Licenses Only

  The discount only applies to full licenses. The pricing remains the same for upgrade licenses.

• Volume Discounts

  We are not offering volume discounts on full Cornerstone 2 licenses while this offer is valid. Volume discounts remain in effect for upgrade licenses.

• Other Discounts and Offers

  We are also not offering student or non-profit discounts on Cornerstone 2 licenses while this offer is valid. However, student and non-profit discounts are still available for upgrade licenses.

  Other offers valid during August 2011 are also limited to upgrade licenses.

It is our policy to support the current and previous versions of OS X in any given release. For example, Cornerstone versions 1.0-1.1 supported 10.4 Tiger & 10.5 Leopard, while 2.0-2.2 supported 10.5 Leopard & 10.6 Snow Leopard.

1.5 and 2.5 were exceptions to this rule. Both were released on the cusp of a new Mac OS X version and provided simultaneous support for three versions of OS X: 10.4-10.6 with 1.5 and 10.5-10.7 with 2.5.

We believe that this policy represents a good compromise between supporting older operating system versions and simultaneously allowing us to migrate to newer tools and keep Cornerstone up-to-date. Unfortunately, it can’t be achieved without leaving something behind.

So, now that 10.7 Lion is here we will be making the next step by dropping support for 10.5 Leopard in the next 2.x update. As a consequence, we will also be dropping support for Macs with PowerPC processors.

We believe that very few Cornerstone users will be impacted by this change. Currently less than 3% of visitors to zennaware.com are running 10.5 Leopard and we think this number will decrease very rapidly as 10.7 Lion is adopted (already almost 30% of visitors are running 10.7 Lion).

However, we do understand that some users will continue to need a version of Cornerstone that runs on 10.5 Leopard. For this reason we will be making 2.5.x available for download from the Cornerstone support page, in the same way as we do with 1.5.

We will continue to support Leopard with 2.5.x maintenance updates up until the release of the next 2.x update.

Future versions of Cornerstone will be Intel-only and will be better for it — removing the PowerPC code means smaller downloads and potentially faster launch times — but we can’t help feeling a little nostalgic.

Leaving the PowerPC behind marks the end of an era.

So long PPC. So long Mac OS X 10.5 Leopard.

We’re really exited to announce that Zennaware is sponsoring this year’s uDevGames contest.

There is a great selection of prizes available and the lucky winner will win a 5-user license for Cornerstone 2!

Other fantastic prizes include BBEdit and Yojimbo from Bare Bones, Reason from Propellerhead and OmniFocus and OmniGraffle from Omni Group.

What is uDevGames? In their own words:

The uDevGames contest is iDevGames’ unique grass-roots game creation contest, established in 2001 to encourage Macintosh game development, and to recognize the best and most innovative developers in the community.

We think it’s a great idea and are proud to be a part of it in our own small way.

Check out the uDevGames site for more information.