5.x

Companion release to the great new Version Control API 5.x-2.0-alpha1. Apart from user-invisible porting work and a more reliable mechanism to recognize re-additions of files as additions instead of modifications, the xcvs-* scripts have been improved in their branch/tag handling, which allows to control deleted tags using generic Version Control API facilities and fixes a couple of problems with tag moves.

Companion release to the great new Version Control API 5.x-2.0-alpha1. Features a link to the Commit Log in the project page, otherwise I can't remember anything user visible that you might notice, apart from the general superiority of the 5.x-2.x API of the module family.

It compiles! Ship it!

Finally, after a long long time of rethinking, refactoring and porting, here comes the first 5.x-2.x release with a fully restored feature set - meaning that it does everything that 5.x-1.x did, or at least it should. A bit of API documentation still needs to be adjusted, but from a user point of view this stuff should be on par with or better than 5.x-1.x in every aspect. The Git and Mercurial backends have not yet been ported at this time, which is probably the only reason why you wouldn't want to try this out.

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.

Rewrote the language functions to load all core RTL CSS files.
Based on code from Amnon Levav

Fixed error displayed when first installing the module. Declared $options as an array() on pcp_admin_settings_form_data() so the form api can handled an empty set of data.

Initial release of module.