Git Migration Status Update

My first official issue as the new project manager for the Git Migration was to write the Status Update. I began by trying to summarize the complex, technical history of the project, but I've come to realize that most of the history is already documented. If you're interested in where the migration team has been, check out the Detailed Background at the end of this post.

Meanwhile, here’s the update I think people are really looking for:

When will CVS be gone forever?

Working with the Git Migration team, we've created the sprint schedule below. Some very large unknowns in terms of resource availability prevent putting calendar dates on the milestones just yet, but we're making progress in securing those resources.

The team has been working in two-week sprints, the third of which concluded Friday, November 5. (Sprint histories are available in the Detailed Background).
 
Below is the tentative sprint schedule, subject to change as we go along and things come up. Please help us to ensure we meet our deadlines!

Sprint Schedule

• Sprint 4 - Release-Worthy Views for VC API and Git Activity Log
  Release-worthy views for Version Control API and for Git activity logs will be demonstrated at the Deliverables Demo on Friday, November 19 at noon PST.
• Sprint 5 - VC API / Project Module Integration
  Specific deliverables for this sprint will be defined during the sprint planning meeting. Lots of behind-the-scenes integration work is expected.
• Sprint 6 - Project Module
  At the end of this sprint we’ll see Release Nodes being automatically generated for repositories containing appropriately named branches.
• Sprint 7 - Preparation for Broader Community testing
  At the end of this sprint, community testers will be able set up a robust test environment
• Sprint 8 - Community Testing
  We’ll see issues opened by the general community making use of git.drupalcode.org as well as low-level testers using local test environments which will be resolved during this and the next sprint.
• Sprint 9 - Community Testing and Deployment Preparation
  Migration Scripts will be 100% finalized and the project poised for release.
• Sprint 10 - Deployment
  CVS will be gone forever

This puts us 14 theoretical weeks from deployment, realistically a bit longer considering the winter holidays but still on track for moving to Git before the Chicago DrupalCon in March 2011.

When it’s done, will it be like github?

No. For the initial deployment, we’re only going to be swapping out the CVS parts of Drupal.org with the Git parts of Drupal.org, not adding any additional features. This is both to help limit the community’s “shock” value to only those with some sort of coding prowess (module/theme developers, patch creators) and also to allow us to migrate much faster!

Later on, we hope to add more community-facing functionality that takes full advantage of our new distributed version control system. But no, this functionality will also not be like GitHub; it will be like Drupal.org and will be tailored to our needs and our history. And realistically, our tools will never quite be able to keep up with the wonderful environment that is github because we are building Drupal modules and themes and core instead!

How can I get involved?

Things you can do to help:

• A small group of committed developers are needed on the actual code revamping. There are code-related issues in the Great Git Migration issue queue. Meetings to organize collaboration on this work are announced in the Git Migration Team Groups.drupal.org group.
• Use git for your development workflow. Many, many of us are already using git for almost all of our git workflow. The git.drupalcode.org repository is already available and works and is a faithful mirror of our CVS repository. This will help flush out bugs, and will make us all better at using the repository before the full rollout. Read about the transitional git workflow many Drupal developers are using.
• Start teaching git at all Drupal get-togethers. Let’s make sure that every Drupal camp or meetup has a git session. One of the biggest worries we had about this whole project was the retraining of the entire community. Presentations and other resources are available to you.
• Come to the Git migration sprint demos! Every two weeks, the Git migration team demonstrates the functionality that has been completed. Community members are encouraged to join us and see the progress being made. Our next demo is happening November 19.

Detailed Background:

• The Why and How of the Git Migration: Evaluation discussion for how to move Drupal.org off of CVS
• The Battle Plan: Migrating Drupal to Git
• Version Control API & Drupal's git migration
• Sprints Summaries: 1 - Decisions, 2 - Version Control API, 3 - Views Integration