versioncontrol 5.x-2.0

The definite release of Version Control API for Drupal 5! Compared to 5.x-2.0-rc2, this one just contains a few bug fixes that I noticed while porting the code to Drupal 6. Here's what changed since the last release candidate:

• Important: Prepared the database schema for the 6.x upgrade - a few indexes weren't named quite the way that the Schema API based table specification in 6.x-1.x would create them. Before upgrading to any 6.x version, you need to install this 5.x-2.0 release and run update.php.
• Fixed watchdog entries when creating, updating or deleting either repositories or VCS accounts.
• Fixed reapplication mail subject in the Version Control Account Status module. (Now with " [reapplication]" appended, like it should.)
• Fixed access permissions to the private VCS account edit page, which might have been denied before in certain cases although access should have been possible.

And because it's the "final" 5.x-2.0 release, let's rehash what has been written in the 5.x-2.0-alpha1 announcement already:

The purpose of the 5.x-2.x series was a major change in how to organize and treat commits, branches and tags. This not only comes with performance improvements (theoretically, not benchmarked) and a massive simplification of code required by backends. It also cuts down on database tables and makes it possible to treat commits, branches and tags (now unified as "operations") in a similar fashion where appropriate. Along the way, 5.x-2.x clears the way for sane repository browser functionality (experimentally implemented in the experimental Repoview repository browser prototype) and generally revamps pretty much everything that is not repository or account specific.

For you as a developer, this means more possibilities with the same amount of code, and stuff that wouldn't have been maintainable before might become feasible now. Have a look at the insane API changes documentation page (fully documents all changes of public functions, as far as I can tell) to get a grasp of the new API and a help for porting your code. You are now officially invited to port the remaining VCS backends (Git and Mercurial), or write new ones (*cough*Bazaar*cough*).

For you as a user, this means that Commit Log now displays commits, branches and tags on a single page. Also included is an attempt at workflow_ng support, although the set of actions and conditions is still rather minimal. (If you want to help out, here's where you can get lots of neat features with little code.) There have been slight usability improvements and various bugfixes in other places too, but essentially there's little more to see here. You should still upgrade just because this stuff is cool, and the Drupal 6 version requires an upgrade to 5.x-2.0 anyways before you can migrate to 6.x-1.x.

Note that Version Control API 5.x-2.0 is not compatible to VCS backends with version 5.x-1.x or earlier, so if you want to run it on the yet unported Git or Mercurial backends, you might want to wait until a 5.x-2.x version is out for those. Otherwise, give 5.x-2.0 a shot. On the surface it's not *just* as much better as a year-long development cycle would promise, but in addition to laying the foundation for future goodness, this release also comes with an assorted share of nice improvements here and there.

Once you're using 5.x-2.0, you won't look back! (Unless you're already running the 6.x-1.x testing releases, which come with the same amount of heart-warming goodness.)