[Maintainers-news] Git migration is live - what you need to do as a maintainer

[maintainers-news at drupal.org]

The Drupal.org CVS -> Git migration has been completed during the evening of
February 24, though the morning of February 25 2011! If you see a member of
the git migration team online or at Drupalcon, be sure to thank them.

There are a number of things that ALL CVS account holders MUST do ASAP in
order to be able to maintain their projects going forward. All write access
to CVS is cut off and you cannot make commits or releases that way. A
comprehensive set of documentation is available at
http://drupal.org/documentation/git [1]. This post is just meant to highlight
a few essential steps for existing maintainers.

Key points:

  * Do you want to be able to make new projects and changes to your existing
    projects? You need to turn on Git access [2] for your account.
  * Do you want credit for your commits? Read about how to set up your Git
    identification [3].
  * Do you want to have a quick way to find Git instructions for your project?
    See the Git instructions [4] tab that is now on each project page.
  * Do you want to be able to access your Git repos without constant prompting
    for passwords? Add one or more ssh keys [5] to your account.

Note that the CVS repositories will NOT get any further updates now that the
migration is complete. They are for historical reference only. You are
strongly encouraged to replace them with git clone versions.


[1] http://drupal.org/documentation/git
[2] http://drupal.org/node/1047190
[3] http://drupal.org/node/1022156
[4] http://drupal.org/node/1072822
[5] http://drupal.org/node/1027094