Since the last update
For a complete list of what’s been accomplished during our last three sprints, see http://bit.ly/fCLGYj
Major achievements include:
- Implementation of git-shell wrapper and proper daemonization of Twisted SSH; allows Git authentication with either SSH keys or username/password.
- Views-powered statistics and commit logs in Version Control API
- Major refactoring and a 6.x-2.x alpha release of Version Control API: http://drupal.org/node/993130
- Verson Control Project and Version Control Git upgraded to 2.x version of Version Control API.
- Addition of sandbox functionality to Project module: http://drupal.org/node/986718
- Prototype for a Drupal-based repository viewer: http://git.howardtyson.com/
- Upstream improvements made to the DBTNG and Views Field View modules.
- The fixing and addition of automated tests for Version Control API.
- Migration scripts at http://git.drupalcode.org/ now auto-updating every 5 minutes.
- Module and reporting developed to detect duplicate project names: http://whiteboard.binaryculture.com/
- Git Deploy module created: http://drupal.org/project/git_deploy
When will CVS be gone forever?
As DrupalCon Chicago draws closer, the Git Migration team has been working hard toward a pre-Chicago release date. We’re striving toward migration during the week of February 14, but choosing the actual date still requires more progress as well as the coordination of people’s schedules before we can pin it down with confidence.
To be ready for that migration window, we’ve put together the following, more detailed sprint schedule which is still subject to change as we go along and things come up. Please help us to ensure we meet our deadlines!
Sprint Schedule
-
(12/20 - 12/31) Sprint 7 - Unblockers for Broader Community testing
At the end of this sprint, git-dev.drupal.org will be ready for community testing of non-push-related code (e.g. project sandboxes, commit log viewer, repository viewer). Project node integration of Version Control API (e.g. maintainer tab, committer statistics, etc.), final decision made on community project creation process. Alpha/beta release of Version Control API + Version Control Git. Project release node integration and packaging scripts. Demos for this sprint and from now on will be done on the git-dev.drupal.org server.
-
(1/3 - 1/14) Sprint 8 - Preparation for Community Testing
(Jan 7: git-dev.drupal.org done and ready for documenting)
All push-related code deployed to git-dev.drupal.org for community testing, finishing touches put on various aspects so no *obviously* buggy things are appearing. Stable release of Version Control API / Version Control Project / Version Control Git. Documentation and test plans. Blessing given to all code by security team/infrastructure manager. At the end of this sprint, announcements far and wide asking community to test git-dev.drupal.org.
Jan 15: CODE SLUSH: NO new features, only bug fixes to existing features
-
(1/17 - 1/28) Sprint 9 - Community Testing and Deployment Preparation
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 sprint. Final bug fixing. At the end of this sprint, we’ll disable users’ ability to choose their mapped email address for the migration, so whatever is chosen at that time will be used forevermore.
JAN 31: CODE FREEZE: Only changing code in emergency OMG situation
-
(1/31 - 2/11) Sprint 10 - Finalizing for Deployment
Migration Scripts will be 100% finalized and the project poised for release. Repeated testing/re-imaging to ensure things are working properly.
-
(2/14) Deployment
CVS will be gone forever Dead Dead Dead RIP.
How can I get involved?
Things you can do to help:
- There’s a narrow window between the completion of features and opening up git-dev.drupal.org for testing. Join http://groups.drupal.org/drupal-org-git-migration-team and, when we’re ready, volunteer to write and test documentation!
- Again, join the Git migration team, and watch for the call for community testers, and help us by testing when we’re ready.
- 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 December 31.