[Maintainers-news] Less than two weeks to prepare for the CVS -> Git migration!

[maintainers-news at drupal.org]

For those not following the Drupal.org home page, the Drupal.org CVS -> Git
migration we told you about last newsletter is scheduled to launch February
17. There are a number of things that ALL CVS account holders MUST do ASAP in
order to prepare for the migration.

*Once the migration is complete, that's it; CVS will be cut off, Git will be
in place. It is /absolutely imperative/ that each and every one of you
perform these steps in advance of the migration.* Thanks for your immediate
attention to this.

Key points:

  * Do you want credit for your commits? Read about how to set up your Git
    identification.
  * Do you want to be able to make new projects and changes to your existing
    projects after February 17? Read about how to test Git on our staging
    site.
  * Do you want people to be able to download your code? Read about how
    reviewing your existing projects' data.

Keep up on the latest news by
http://groups.drupal.org/drupal-org-git-migration-team or Twitter:
https://twitter.com/drupalgitgremln.

-------- SET UP YOUR GIT IDENTIFICATION  
--------------------------------------

Git associates commits with a name and e-mail address, rather than a username
as in CVS. In order to ensure that you are properly credited for both your
legacy and future contributions post-Git migration, please complete the
following steps *by February 13*:

  * Download and install Git. There are lots of resources on the Internet
    about how to do this. http://book.git-scm.com/2_installing_git.html is
    one.
  * Specify your desired full name and e-mail address to associate with your
    migrated CVS commits in your drupal.org user profile:
    http://drupal.org/node/1018116
  * Use the instructions at http://drupal.org/node/1022156 to identify
    yourself to Git with your specified name and e-mail address. This will
    ensure all future commits are also credited to your account.
  * If you wish to use another e-mail address (for example, one associated
    with your GitHub account), http://drupal.org/node/1018118 has instructions
    on how to associate additional e-mail addresses with your Drupal.org
    account.
  * If you don't like your current CVS username and want to switch it when we
    migrate to Git, you have *exactly one and only one chance to change it*.
    Leave a comment at http://drupal.org/node/1036140 with your current CVS
    username, your Drupal.org user ID, and your desired Git username.
    [A-Za-z0-9._-] are the allowed characters.

For more information, see http://drupal.org/node/1037478.

-------- TEST THE GIT MIGRATION  
----------------------------------------------

The Git migration team has set up http://git-dev.drupal.org/, a staging
server where you can test your day-to-day maintainership tasks and
familiarize yourself with Git. There is a helpful screencast at
http://vimeo.com/19467580 which walks through everything you need to (and
can) do, and http://drupal.org/help-test-cvs-git-migration contains the text
version.

Important notes (READ ME!):

  * *Testing will only be open during certain hours of the day*. During this
    pre-launch period we're also going to be doing performance optimization
    and integrating new code to fix bugs, so to allow ample time the server
    will have certain "blackout" periods. There is a wiki page at
    http://groups.drupal.org/node/119449 which contains the current status of
    the system as well as rebuild schedules. Read the Apache password prompt
    on http://git-dev.drupal.org. It will tell you the current state of the
    system.
  * *To log in to http://git-dev.drupal.org/, you must first reset your
    password.*. This is a basic security precaution for our development sites.
    You can do this from http://git-dev.drupal.org/user/password.
  * */All/ users, including current CVS account holders, need to agree to
    terms of use in order to obtain Git access.* There are instructions for
    doing this at http://drupal.org/node/1047190.
  * *The server will be rebuilt every two days.* Each time that happens,
    you'll lose any projects and code changes you made, and also need to
    repeat the "reset password" and "agree to git terms" steps /again/ in
    order to continue testing.
  * *If you find problems, please log them against the Git Migration Community
    Testing issue queue (http://drupal.org/project/issues/git_dev).* Make sure
    whatever you're reporting doesn't show up in our list of known issues [1]
    first. One of our team members will triage bug reports and support
    requests, and then push them into the correct issue queue, if necessary.
    There is also a #drupal-gitsupport channel on irc.freenode.net for new Git
    users (and experienced Git users who want to help make the transition as
    smooth as possible :)).

-------- REVIEW YOUR EXISTING PROJECTS' DATA  
---------------------------------

One aspect of the migration is pulling in all legacy CVS data and converting
it to Git. It's important to check over your own projects' data and ensure it
looks correct.

  * Does http://git-dev.drupalcode.org/ show the proper branches/tags for your
    projects, and list the proper commits associated with the proper users?
  * Have your commit messages been imported in properly under the "Your
    commits" and "Project commits" views on git-dev.drupal.org?
  * When you download tarballs and zipballs of your project releases, do they
    extract cleanly, and contain what they should?
  * Do they install properly and function as they should?

-------- HELP US!  
------------------------------------------------------------

And finally, if you already know Git well, please:

  * Hang out in #drupal-gitsupport to help support new users.
  * Help with support requests and cleaning up duplicate issues in the Git
    Community Testing queue: http://drupal.org/project/issues/git_dev
  * Help write or improve the documentation: http://drupal.org/handbook/git

We need all the help we can get in order to make this as smooth a transition
as possible! Once Git goes live, CVS is dead, dead, dead. Hooray!


[1]  
http://drupal.org/project/issues/search/git_dev?text=&assigned=&submitted=&participant=&issue_tags_op=or&issue_tags=Known+Issues