Development:Switching Moodle main code repository to Git: Difference between revisions
From MoodleDocs
Line 22: | Line 22: | ||
===Next steps=== | ===Next steps=== | ||
* branch MOODLE_20_STABLE from HEAD in CVS | * branch MOODLE_20_STABLE from HEAD in CVS | ||
* create new MOODLE_20_STABLE branch form master in git | * create new MOODLE_20_STABLE branch form master in git | ||
* 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 | ||
Revision as of 06:49, 13 December 2010
Necessary changes on moodle.org servers
Reconfigure CVS server
- stop automatic weekly tagging and daily version commits in CVS
- stop automatic cvs.moodle.org --> git.moodle.org export
- take away all CVS write access from main CVS moodle module at cvs.moodle.org (keep all contrib and lang modules unchanged) - only moodlerobot and CVS admin will have write access
Sync CVS with Git
- make binary snapshot from git cvshead to CVS HEAD - override CVS checkout with files from current cvshead Git branch
Tweak git://git.moodle.org/moodle.git
- give write access to Sam, Petr, Eloy and Martin
- 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)
- 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)
- create new master branch from cvshead
- delete old cvshead branch in Git (the master is the correct name now)
Set up git://git.moodle.org/integration.git
- give write access to Sam, Petr, Eloy and Martin
- configure Pull project to track this repo
Next steps
- branch MOODLE_20_STABLE from HEAD in CVS
- create new MOODLE_20_STABLE branch form master in git
- set up 3 QA moodle sites on top of the integration git repo
Already done
- create PULL project for requests
Other
- create a separate repository or branches for the amos bot commits in /install/xx/