Difference between revisions of "Switching Moodle main code repository to Git"

Jump to: navigation, search
(Next steps)
(Potential problems)
Line 21: Line 21:
 
# set up 3 QA moodle sites on top of the integration git repo
 
# set up 3 QA moodle sites on top of the integration git repo
  
==Potential problems==
+
==Other==
* Find out how and where to allow amosbot to commit lang strings for /install/
+
* create a separate repository or branches for the amos bot commits in /install/xx/
  
 
[[Category:Git]]
 
[[Category:Git]]

Revision as of 04:02, 25 November 2010

Necessary changes on moodle.org servers

  1. stop automatic weekly tagging and daily version commits in CVS
  2. stop automatic cvs.moodle.org --> git.moodle.org export
  3. take away all CVS write access from main CVS moodle module at cvs.moodle.org (keep all contrib and lang modules unchanged) - only moodlerobot will have access
  4. make binary snapshot from git cvshead to CVS HEAD - override CVS checkout with files from current cvshead Git branch
  5. branch MOODLE_20_STABLE from HEAD in CVS
  6. tag 2.0 in CVS
  7. create new master branch from cvshead in git.moodle.org
  8. create new MOODLE_20_STABLE branch form master in git.moodle.org
  9. tag 2.0 in git.moodle.org
  10. delete old cvshead branch in Git (the master is the correct name now)
  11. set up git commit hooks that push mirrors to Github and Gitorious from git.moodle.org (all 4 branches, we need to set up keys for the moodlerobot)
  12. set up git commit hook that triggers export to CVS commit mirror (all 4 branches, we need to tweak the PHP script and keys for CVS commit access)
  13. give git write access to sam, eloy, martin, skodak on git.moodle.org/moodle.git
  14. configure jira to track git://git.moodle.org/moodle.git

Next steps

  1. set up integration git repo at git.moodle.org/integration.git
  2. give git write access to sam, eloy, martin and skodak on git.moodle.org/integration.git
  3. configure jira to track git://git.moodle.org/integration.git
  4. set up 3 QA moodle sites on top of the integration git repo

Other

  • create a separate repository or branches for the amos bot commits in /install/xx/