This module will be deployed as part of the d.o conversion from CVS to git, but it's been left alone long enough that it needs re-reviewing to see what must be done to catch it back up with both vcsapi and project.
So, yeah, kind of a meta-issue.
This module will be deployed as part of the d.o conversion from CVS to git, but it's been left alone long enough that it needs re-reviewing to see what must be done to catch it back up with both vcsapi and project.
So, yeah, kind of a meta-issue.
Comments
Comment #1
marvil07 commentedYep, we need to review this, actually AFAIK it do not work with 2.x since OOP conversion.
In the other hand I think we should wait until #831896: Refactor VC API to use DBTNG & an Entities-like system is commited since it's just another API change \o/
Comment #2
hunmonk commentedadding redesign tags
Comment #3
sdboyer commentedAdding this to the current sprint; this'll be where I post everything relevant, and that'll hopefully unblock project* folks on us.
Comment #4
webchickMarking as something to sort out this sprint.
Comment #5
sdboyer commentedI've emailed notes to dww, and made a commit that notes where a lot of changes need to be made: http://drupal.org/cvs?commit=423844
Marking CNW b/c dww still needs to do his review, then he and I need to plan.
Comment #6
drummComment #7
sdboyer commentedadding git sprint 2 tag
Comment #8
webchickComment #9
sdboyer commentedI've done my bit, it's dww's show now :)
Comment #10
eliza411 commentedI'm assigning this to me until I've secured dww's time to work on this.
Comment #11
eliza411 commentedTime secured, time tentatively scheduled for Friday, November 5.
Comment #12
mikey_p commentedComment #13
eliza411 commentedAssigning this to Sprint 4.
Comment #14
eliza411 commentedTagging git sprint 5
Comment #15
dwwmikey_p and I have completed a google doc outlining all the remaining work, which we've shared with the Git migration team. We have a meeting tomorrow to go over the doc. Calling this fixed.
Comment #16
aaron.r.carlton commentedsubscribe.
I would like to track this project's progress. I've got the 6.x-2.x-dev installed alongside the 6.x-2x branches of versioncontrol_api, and versioncontrol_git. Errors in this project are definitely due to it being out of date with the latest changes to those projects. Are you planning to translate the Google doc into the issues queue so the community can get an idea of what's left to be done til a new alpha release?
Comment #17
dwwYes, there will be issues for everything that aren't already in the queue. But the code for this particular module is going to be almost entirely removed in the 6.x-2.* series and re-written from scratch.