Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal.org needs this to move to D7.
Next Steps
Now that an -alpha1 has been tagged, the Git Team is closing this meta issue in favor of tracking the rest of the work under the versioncontrol-6.x-2.0-release-blocker tag.
Comments
Comment #1
marvil07 CreditAttribution: marvil07 commentedPostponed at least until we have clear the plan for 6.x ;-) #893012: [meta] Blockers to a 6.x-2.0 release.
Comment #2
marvil07 CreditAttribution: marvil07 commentedAnd we at least have tag now!
versioncontrol-6.x-2.0-release-blocker
Let's revisit this when we have a tarball for 6.x-2.0
Comment #3
likewhoa CreditAttribution: likewhoa commentedsubscribing
Comment #4
mrsinguyen CreditAttribution: mrsinguyen commentedsubscribing
Comment #5
timonweb CreditAttribution: timonweb commentedsubscribing
Comment #6
c.david CreditAttribution: c.david commentedsubscribing
Comment #7
ericduran CreditAttribution: ericduran commentedFYI, if anyone wants to help I started a D7 sandbox -- http://drupal.org/sandbox/ericduran/1275132
Please be nice, this is a sandbox project for my own purposes. I know the 6.x version is still a work in progress. Just letting people know in case they're interested.
This sandbox project will never become a full project, if when the version control maintainers start working on a 7 branch they're welcome to look at my code, and start from there or not. ;-)
anyways still a work in progress just an fyi.
Comment #8
ericduran CreditAttribution: ericduran commentedFYI: for the maintainers, the d7 port on the sandbox above isn't complete but its usable right now, I'm still missing some work, but its hard to find all the issues without a project using it. So I also started porting the version_control_git to d7 (http://drupal.org/sandbox/ericduran/1288456) which is also pretty usable.
I'm working on commitlog now. But right now you should be able to see all your logs, with the correct user mapping, and the feeds. Still missing some work.
I'll be trying to track the D6 branch for any changes, Also I'm willing to co-maintain the d7 branch if you guys decided to use any of the code in the port. Just an FYI.
Also is there any group where discussions take place? Also I'm also working on a port to d7 for repoview for git.
Comment #9
mprocte1 CreditAttribution: mprocte1 commentedsubscribing
Comment #10
ericduran CreditAttribution: ericduran commentedSo my port is behind a couple of patches. but it should still be good.
This is more than ready to test. I've been running it locally for some time now.
The amount of changes required weren't really much but you can review the fork over at http://drupal.org/sandbox/ericduran/1275132
Also I have a version_control_git port that should also be ready to review.
I'm missing some clean-up when I do, I'll post a patch here. I'll also try to catch up on the latest commits.
All feedback welcome.
Comment #11
cerdiogenes CreditAttribution: cerdiogenes commentedWhen I try to clone your port I get the following:
warning: remote HEAD refers to nonexistent ref, unable to checkout.
The folder created by clone only have .git and nothing more. What can I do to download your port?
Comment #12
Jackinloadup CreditAttribution: Jackinloadup commented@cerdiogenes
Try this, it will checkout the only branch he has
git clone http://git.drupal.org/sandbox/ericduran/1275132.git versioncontrol_7_sandbox -b 7.x-2.x
Comment #13
migmedia CreditAttribution: migmedia commentedIt's round about a year of silence in this project (last code-changing commit 2011-05-22).
migmedia
Comment #14
marvil07 CreditAttribution: marvil07 commentedI guess you are not looking at the right place, please see http://drupal.org/node/148301/commits (6.x-2.x branch)
I would say healthy, but not so active.
Definitely, it will have a D7 branch.
Please take a look to the current issue queue, you have a little summary at #893012: [meta] Blockers to a 6.x-2.0 release, but in general the most important issues are on the versioncontrol-6.x-2.0-release-blocker tag as mentioned there. Any help is welcome :-)
BTW, about this issue, I will be pretty happy to go with the D7 version but after having a stable 6.x-2.x released, not before.
Comment #15
holtzermann17 CreditAttribution: holtzermann17 commentedNote that this is related to a proposed Google Summer of Code student project, see top of http://groups.drupal.org/node/138009 -- interested students may consider applying (student applications will be accepted March 26 19:00 UTC to April 6 19:00 UTC).
Comment #16
ericduran CreditAttribution: ericduran commented@holtzermann17 :-/ My sandbox already has a D7 port. I haven't touch it in a while, but I think we should sprint tomorrow at Drupalcon, I'm not sure it'll be enough work for a google summer of code.
Comment #17
cvangysel CreditAttribution: cvangysel commentedI actually wrote a GSoC proposal to port the VCApi to D7, you can find it here: http://groups.drupal.org/node/219999
Next to the VCApi I would also like to port vcapi_git, vapi_project and all the activity stuff I did last year. Your D7 port also doesn't include the generic-reposync and event-entities stuff, am I right?
Comment #18
webchickTagging for sprint.
Comment #19
tizzo CreditAttribution: tizzo commentedSome D7 port related commits:
Updating for D7 doc comment standards.
Adding an implementation of hook_registry_files_alter() to load our interfaces file before ctools starts loading our plugins.
Fixed a typo
Preventing a notice from being thrown
Comment #20
marvil07 CreditAttribution: marvil07 commentedRelated: #1545710: Fix tests on d7 topic branch
Comment #21
marvil07 CreditAttribution: marvil07 commentedComment #22
frankcarey CreditAttribution: frankcarey commentedAnyone have any more status updates post DrupalCon?
Comment #23
marvil07 CreditAttribution: marvil07 commentedLots of progress since May(see
git log --since="May 16th, 2012" --oneline 7.x-1.x
), but not really specific to D7 port, but instead about bringing awesomeness and stability to the module.In the other side, the API is working(you can almost say ported) on D7 :-), but I guess we still need some views-related fixing. When that is done I guess we can close this and start with individual issues.
Also, it worths to remember that we(at least I) want to release a stable 6.x-2.0 before closing this.
Comment #24
marvil07 CreditAttribution: marvil07 commentedA lot of D7/views3 related porting is now done, so I would say this D7 port is mainly ready.
I guess it's time to look back to #893012: [meta] Blockers to a 6.x-2.0 release.
PS: This issue is meta: we are not attaching patches here, and instead adding changes directly.
Comment #25
Senpai CreditAttribution: Senpai commented@marvil07, since #893012: [meta] Blockers to a 6.x-2.0 release is closed in deference to the versioncontrol-6.x-2.0-release-blocker tag, please roll an alpha1 of this 7.x code branch and let's close this meta issue.
Comment #26
marvil07 CreditAttribution: marvil07 commentedRelease node added: 7.x-1.0-alpha1(just waiting on the tarball for node publishing).
Comment #27.0
(not verified) CreditAttribution: commentedversioncontrol-6.x-2.0-release-blocker