Releases for Version Control API

Changes since 7.x-1.0-rc2:

• by drumm, marvil07: Improve commit message sanitization.
• Prevent adding empty vcs condition on repository controller.
• New option for drush vc-sync to force repository unlocking.
• #1796144 follow-up: Catch unknown exceptions on event processor plugin execution.
• #1796144: Added an event processor plugin type for repositories.
• Minor fixes on example backend to pass tests.

Changes since 7.x-1.0-beta2:

Changes since 7.x-1.0-beta1:

• #1293956 follow-up: Fix repository getSynchronizerOptions method.

An important bugfix related with the new option for reposync plugins to store tag/commit relations optionally.
a.k.a. let's fix the tests for backends implementing it.

Changes since 6.x-2.0-beta7:

• Let simpletest execute the right hook_boot(dbtng) on its setUp.
• #723962 by tizzo, marvil07: Code standards review.
• Only fire code arrival hook when synchronization was successful.

Changes since 6.x-2.0-beta6:

• VersioncontrolRepository::titleCallback() should reference $this.
• #1642326 follow-up: Fix db_query call, its D6 db_query, not D7's.
• #1291904 by tizzo: Complete hooks documentation.

Changes since 6.x-2.0-beta4:

• #1001480 follow-up by marvil07 | hoesi: Let pseudo-empty non-array values to be attached to the controller query.

Changes since 6.x-2.0-beta2:

Porting to D7 in progress.

Some API changes, lots of bug fixes, some improvements on tests and better default views.

Some relevant commits:

• d5a37f4 task #970244: Create a views handler to map operation author/committer to their drupal user
• 498eba2 Issue #999564: Created a views handler for the item revision 'action' field, and updated the default view with it.
• 64a2a8b Issue #999652: Reorganize VCAPI's menu structure so it's no longer Project*-centric.
• 8ca277b Issue #1010398: Create a drush command to run repo log fetching.
• e39b8c9 Add a new drush command for updating operation author/committer mappings.
• dc843dc Issue #979066 by mikey_p, sarah_p: Add a visual diffstat views field.
• 8cec713 Issue #983926 by marvil07, sdboyer: Remove VersioncontrolAccount class, and many other account-related pieces that simply will not be ready for release.
• 5e67645 task #723958: Remove ArrayAccess dependency everywhere.
• 87ba390 Issue #1016504: Batch repository synchronization drush command.

Latest & greatest of Version Control API.

There hasn't been a release in a while - partly because of DrupalCon DC business, partly because of other responsibilities, and partly because I wanted to make sure the new versioncontrol_release module in versioncontrol_project can work as intended with the exposed API. As a consequence, a number of API functions have been added or changed since the last beta was released.

In addition to API happenings, there have been visible bits of progress all around:

• Fixed a large number of PHP notices, hopefully all are now gone.
• Fixed prevention of similar VCS usernames being registered.
• #396212 by greggles: Implemented feed autodiscovery for the commit messages page.
• Postgres compatibility fix in the "Most active developers" block.
• #418086: Simple commit filters without HTTP attributes in Commit Log - use paths like "commitlog/repo/1", "commitlog/id/543", "commitlog/uids/1,2,3", etc.
• Show correct VCS account editing form for users when the respective user has multiple accounts registered.

In comparison to beta3, this release contains an assorted share of bug fixes, mainly targeting the commit messages view which should work much better now. Also, the account export page works again for the CVS backend, and the autocomplete callback works too so the project node integration module (now releasing its initial beta for Drupal 6) can again complete usernames in the commit access administration page.

Hotfix update. A single stupid bug caused the whole administration area to yell out a fatal error, so let's have the *real* beta1. That name is already taken, so it's beta2 now.

First testing release of Version Control API for Drupal 6. Use together with the 6.x-1.x-alpha1 versions of the CVS and/or the SVN backend. All features from the 5.x-2.0 release except Rules integration should be working already, and bug reports about stuff that doesn't work will be appreciated.

Second release candidate. This one fixes a PHP error when trying to browse non-existent directories, and adds a "message" filter to Commit Log (because cvs.module also has it). Other than that, no changes in Version Control API itself. (The CVS backend gets a much improved release, though.)

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.

The stable 5.x-1.x branch, barely maintained anymore since development efforts are nowadays directed at 5.x-2.x and beyond.

5.x-1.1 is a relatively minor bugfix release as follow-up to the last week's large 5.x-1.0, usable as drop-in replacement for the latter. Though this is not the largest batch of fixes, I'm releasing 5.x-1.1 because I'm now branching off the 5.x-2.x branch and will only apply the most pressing fixes to the 5.x-1.x series. So this branch is mostly frozen from now on.

Bug fix only release. The fourth release candidate improves on the third one by including the following fixes:

• Use drupal_urlencode() instead of plain PHP urlencode(). Makes for prettier slashes in Commit Log URLs.
• Don't choke on empty account lists. Also, improve the query functions so that empty constraints (that are set, though) are handled correctly.
• On uninstalling, don't forget to remove the {versioncontrol_repository_metadata} table.

Howdy, comrades! The time has come to mark the API module as (hopefully) stable and feature complete. I'm quite sure that it might not be perfect at all, but it should be worthy of being called 1.0. In order to make sure it is, I need your help: try out this module on your favorite CVS server (in collaboration with the CVS backend) and find bugs, or use it in order to develop another backend (Subversion, Bazaar, ...whatever) and find even more bugs while doing so.

This release marks the milestone of being able to do everything that the original cvs.module could do, or provide the respective functionality to backends and extension modules. Except for one part, which is release node integration: The API as is will probably not completely suffice to get a full-featured port of project_release running. API changes and additions to make this possible will happen in the DRUPAL-5--2 branch, or during the Drupal 6 port, or not at all yet (depends on how Derek wants to tackle the release node integration problem).

As always, the changes since the last release (1.0-beta1, which unfortunately didn't show up on the front page because I forgot to switch from 0.x to 1.x):

Seems that I didn't release a stable snapshot for some time, so let's have one.
Commit notification mails are now implemented, and as this was the last major feature for getting on par with cvs.module, we're now arriving in the 1.0 beta series.

Changes since the last release:

Single, but important bug fix: the commit restrictions were not properly displayed in the repository edit form.

Status and repository filters for the account list, PostgreSQL support, and proper parameter construction for the has_{branch,tag}_access() hooks.

The list of TODO items grows smaller! 1.0 is not far!