o(ther)l/log

I made a few changes to S3 Browser this week. Not exactly new features or impressive bug fixes, but changes in how I'm coding and releasing S3 Browser.

First I moved my source repository to the objc-s3 project on Google Code Hosting, I was waiting for svnsync support, to be able to import my own subversion repository without losing history. So you can now checkout source code for S3 browser. This also means that I might not do source release for absolutely every minor version, but I always tag released versions in svn.

I was already using the issues tracker in Code Hosting. However I will probably not use the downloads area, the fact that it is not possible to remove a download is immediate show-stopper for me. If I ship a version with a very serious security problem (not likely considering what the application does with the keychain, but you never know), I want to be able to remove it as soon as possible. Ditto for a version that would have a major bug, deleting local files etc. "Tagging as obsolete" is not enough.

The only things I'm really missing from Trac are: a good SVN browser, the project Timeline, and automatic links in ticket numbers, revisions and changeset.

Another important change: I now use the Sparkle framework to manage application updating. I released a 1.0.2 with minor bugfixes and auto-update support. At launch, it should check the appcast feed and propose a 1.0.3 (one minor change, it's only to check update is working). Expect more frequent releases.