Major issue #3: Port to Drupal 6
jpetso - January 31, 2008 - 17:08
| Project: | Version Control API |
| Version: | 5.x-1.1 |
| Component: | API module |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Description
After Major issue #1 and Major issue #2 have been tackled, there's nothing that should hold up a port to Drupal 6. Marking as critical too, because we need this for rolling out Version Control API & friends on drupal.org.
#1
just subscribing... any estimates on when this might be ready?
#2
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.)
#3
As part of my SoC project here's my first patch. Doesn't work yet - it's just the beginning. =D
#4
subscribing
#5
I'd like to help. Already ported a simple module (technorati) from D5->D6. I'll see what I can do here.
#6
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.