Difference between revisions of "Git Migration"

From OpenEMR Project Wiki
 
Line 19: Line 19:


==Official git Mirrors==
==Official git Mirrors==
* github
*<b>github</b>
:* repository link: git://github.com/openemr/openemr.git
:* repository link: git://github.com/openemr/openemr.git
:* web page link: http://github.com/openemr/openemr
:* web page link: http://github.com/openemr/openemr
:* mirrors from Sourceforge repository every 30 minutes via an external script
:* mirrors from Sourceforge repository every 30 minutes via an external script
*gitorious
*<b>gitorious</b>
:* repository link: git://gitorious.org/openemr/openemr.git
:* repository link: git://gitorious.org/openemr/openemr.git
:* web page link: http://gitorious.org/openemr/openemr
:* web page link: http://gitorious.org/openemr/openemr
:* mirrors from Sourceforge repository every 30 minutes via an external script
:* mirrors from Sourceforge repository every 30 minutes via an external script
*repo.or.cz
*<b>repo.or.cz</b>
:* repository link: git://repo.or.cz/openemr.git
:* repository link: git://repo.or.cz/openemr.git
:* web page link: http://repo.or.cz/w/openemr.git
:* web page link: http://repo.or.cz/w/openemr.git

Revision as of 22:44, 11 November 2010

Overview

On 10/30/2010, the official OpenEMR repository was moved from cvs to git on Sourceforge.

Migration Details

The massive sourceforge thread that discussed this migration can be found here: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/1412511

Also some discussion on this thread: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3894279

Plan to put more details on the migration, git settings, and mirroring mechanism here.

Items still left to do

  • PROBLEM: When compared the cvs and git repositories, all tags/branches were identical, except for the v3_1_0 tag and the rel-310 branch.
  • SOLUTION: Did not include the rel-310 branch in the migration. Will rebuild it after the migration. While rebuilding rel-310 will also add a v3_1_0_FIXED tag with appropriate code. So will require following steps:
  1. Create a rel-310 branch off the rel-320 branch in the git repo.
  2. Create a diff patch between rel-320 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch, and then tag this with v3_1_0_FIXED.
  3. Create a diff patch between rel-310 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch.

Official git Mirrors

  • github
  • gitorious
  • repo.or.cz

Proposed Developer Structure

Migrated this section to Repository work flow structure page.