Drupal.org Git Team

I wrote a simple script to work with git and sync back to drupal.org CVS automatically: http://klausi.fsinf.at/git-cvs-export

So impatient people like me can move to git now and forget CVS :-) (well, not completely, you need to setup synchronization for each new branch you want to sync to CVS).

One of the Git migration issues closed out this week was Determine branch/tag naming restrictions in Git.

The big news? All branch/tag naming restrictions at the version control system level will be lifted once we move to Git. w00t! Why is that so cool?

Currently, drupal.org CVS restricts you to branch names meeting a specific pattern (DRUPAL-6--2, DRUPAL-7--1-2-BETA1, and so on). If it doesn't match the pattern, it's rejected. This is nice for enforcing consistency in our diverse contributor community.

However, in a distributed version control system workflow, it's much more common to spin off separate branches for features, for bug fixes, or heck, just because you feel like it. And once Git is implemented, you can! Lifting this restriction is going to be pretty huge; it'll mean that going forward, Drupal developers will be able to leverage the full power of Git in their day-to-day workflow. Awesome! :D

However, in order to facilitate key community infrastructure such as Update Status and the testing bot, the tags/branches you intend to translate into actual releases (and tarballs) on Drupal.org will have to follow a consistent naming convention, similar to what's done now, but much more human-readable:

So in summary, you'll have the freedom to branch early and branch often while in development, and use much less obtuse names for your tags/branches when you're ready to release. Yeehaw! Thanks a lot to sdboyer and dww for working this out!

I've been chatting with folks about this idea for a while, and it's now time to write it up and get it moving. Summary version: as part of/in tandem with the Git migration, I want to create a set of git-for-Drupal training tools. There's a particular structure I have in mind for how these tools should work:

• First, we define our different target users/audience. For git, some the obvious groupings are "authors & maintainers" and "patch contributors"

Hello Git Migration Team.
I am interested in sharing plans to teach Git.

In the beginning of July, I will be teaching a Git class to students participating in a summer Drupal learning project.

This is my plan for preparing the class:
1. Personally get more up to speed with Git. I use Git already, but want to read both Git books (the O'reilly one & also the Apress book) Both are mentioned on the Drupal Git resources handbook page.

* http://drupal.org/node/783086

* http://groups.drupal.org/node/64083 (learning Git discussion)


is here - http://drupal.org/community-initiatives/git/feature-list

Tell us a little bit about who you are, what your background is, what area you're able to help with, and most importantly, what you have time to do! :)

The branch and tag naming conventions are kinda old and crusty. Thanks to a feature of the migration script we'll be using to move to git, we have the option of changing our branch and tag conventions, and renaming all of the old crusty ones at the same time. That means we could actually do a clean migration to a new naming convention - and that we'll probably never, EVER have another opportunity to do so.