sadly, Version Control API won't be ready in time for the 6.x deployment of drupal.org, so this module is going to have to limp along for another release cycle... :(

Comments

dww’s picture

dww
we/he/they
commented

Yup. :(

Note: a lot of this porting could happen now. The big chunk that will a) be the worst code to port and b) will have to wait, is all the project_release integration. However, all of that should probably be split into a cvs.project_release.inc file, anyway, as we do the D6 menu split for this module.

So, this issue is definitely "active", since someone could make a lot of progress (all the code for managing CVS accounts, displaying commits, etc) right now.

Thanks,
-Derek

dww’s picture

dww
we/he/they
commented

Note: while someone can work on a patch for this right now, we can't actually start committing anything until http://drupal.org/node/209417 is done. That should be pretty easy, but if anyone wanted to help with that, it'd be much appreciated.

hunmonk’s picture

hunmonk commented
Status: Active » Fixed

the 6.x port is done, at least as done as we can get it w/o having project* converted yet. the xcvs scripts required no adjustments at all, and i've tested pretty much all the functionality in the ported code -- should be pretty easy from here.

check #225059: Port cvs.module project integration to D6 for the remaining to do items for project 6.x functionality.

hunmonk’s picture

hunmonk commented

tested as working on both mysql and pgsql, committed to 5.x-2.x, deployed on d.o, et. all.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.