Major issue #3: Port to Drupal 6

Before starting the port, I want to release a 5.x-2.0 version, and that one comes with rather large changes in the database and a few changes in the API. That means a good amount of work left, I hope to get to do the Drupal 6 port sometime in mid March or something. (Subject to change, depending on how fast the module progresses.)

jandd: If you want to help, please get in contact with Sam Boyer (sdboyer) and avoid continuing this initial patch. As adebar's Summer of Code project failed, we decided that the better course of action would be to finish the 5.x-2.x branch and only afterwards go for a Drupal 6 port. Therefore, the above patch is relatively obsolete because it hasn't been doing a lot anyways, and Version Control API will change quite a bit before the D6 port is tackled. After the 5.x-2.0 release is done, it will probably be easier to start the port from scratch.

So finishing the 5.x-2.x version is the important thing right now. I talked with Sam on how to do that, if you want to help then please get to know functionality and code (preferably starting with 5.x-1.x as it actually works) and then coordinate the tasks you'd like to tackle with Sam. As mentioned in various places, I for myself am not in a position to work on this right now.

So, 5.x-2.0 is nearly done. The D6 port will start in December still, although I don't know how long it's gonna take (it's a good amount of code to port, so it might take a while too). But fear not, there's now two of us taking care of this thing. Good times ahead!

The port is ON! Version Control API and related modules will be ported to Drupal 6 in HEAD, and the previous development branch (DRUPAL-5--2) is frozen except for bug fixes.

If I haven't missed anything, the HEAD version should be fully functional now, except for a few minor shortcomings: the versioncontrol_project module still needs to wait for the completion of the Project module's D6 port (and probably needs a few adaptions then), and the integration with Rules (previously workflow_ng) is not yet adapted to Rules' D5->D6 API changes.

Furthermore, Version Control API's 5.x-2.0 needs a few database indexes to be renamed so that the table structure fits the 6.x one that is described by the new Schema API. Because of that, there are still no testing releases for the 6.x version.

There are a few more points that can be improved for a "proper" Drupal 6 port, e.g. replacing the now deprecated 'value' type form elements with $form['#myvalue'] variables, or getting $form_values out of hook_versioncontrol_extract_{repository,account}_data(). (The latter could also be renamed to hook_versioncontrol_{repository,account}_submit(), which is what Rules does too, and it probably looks nicer.)

The database changes are there. I now need to rework a query so that the "empty" item (which was necessary to remove from the database) is not required, and after that you'll get a first testing release.

Testing releases are out, and upgrading from 5.x-2.0 works - if you want to try a working but not-yet-stable release, you might enjoy the alpha1 already. I'd say the port is nearly done, so it can't be too long until a first stable 6.x-1.x release (famous last words).

All functional changes have been implemented, have a look at the 6.x-1.0-beta1 release notes for slightly more information. I'm just going to close this issue as fixed, please report any bugs in separate new issues. Thanks for stopping by, and have a lot of fun with Version Control API for Drupal 6!