Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Git Migration.

Obsolete:Git Migration: Difference between revisions

From MoodleDocs
(first draft - far from complete.)
 
No edit summary
Line 1: Line 1:
= Proposal to move Moodle development from CVS to some other revision control system =
= Proposal to move Moodle development from CVS to some other revision control system =


Line 13: Line 12:


== Problem that might be solved by a CVS gateway ==
== Problem that might be solved by a CVS gateway ==
* The translation team would have problems moving away from CVS, so we must keep a read/write CVS repository for the time being, to give people time to change over;
* The translation team would have problems moving away from CVS, so we must keep a read/write CVS repository for the time being, to give people time to change over;
* public (read-only) mirrors are providing CVS access, used by people to update their site, we can't break this system
* public (read-only) mirrors are providing CVS access, used by people to update their site, we can't break this system
* replacement for current integration in tools (git in Eclipse? VCSCommand for vim? TortoiseCVS? Etc.).  VCSCommand supports Git now, but for the others, they're still all works in progress.
* replacement for current integration in tools (git in Eclipse? VCSCommand for vim? TortoiseCVS? Etc.).  VCSCommand supports Git now, but for the others, they're still all works in progress.
* there is a [http://wiki.eclipse.org/EGit/Proposal proposal] to create an Eclipse integration plug-in (unresolved)
* there is a [http://wiki.eclipse.org/EGit/Proposal proposal] to create an Eclipse integration plug-in (unresolved)


== Others ==
== Others ==
* Need to see if cvsspam (for the cvs-commits list) would still work
* Need to see if cvsspam (for the cvs-commits list) would still work
* Moving cvs.moodle.org to git.moodle.org? Or keep both?
* Moving cvs.moodle.org to git.moodle.org? Or keep both?


[[Category:Developer]]
[[Category:Developer]]
[[Category:Developer tools]]
[[Category:Developer tools]]

Revision as of 10:10, 23 June 2008

Proposal to move Moodle development from CVS to some other revision control system

There have been discussions to abandon CVS as the main version tracking system, to move to a distributed system instead. Many developers have expressed their interest for Git. A discussion is taking place in moodle.org forums about a possible move to Git.

Some other systems have been mentioned, such as Mercurial.

Moving to Git

Blocker

Jira support: there is a feature request for support in Jira (unresolved). This might not be solved by a CVS gateway, as the current software doesn't keep the same version numbers.

Problem that might be solved by a CVS gateway

  • The translation team would have problems moving away from CVS, so we must keep a read/write CVS repository for the time being, to give people time to change over;
  • public (read-only) mirrors are providing CVS access, used by people to update their site, we can't break this system
  • replacement for current integration in tools (git in Eclipse? VCSCommand for vim? TortoiseCVS? Etc.). VCSCommand supports Git now, but for the others, they're still all works in progress.
  • there is a proposal to create an Eclipse integration plug-in (unresolved)

Others

  • Need to see if cvsspam (for the cvs-commits list) would still work
  • Moving cvs.moodle.org to git.moodle.org? Or keep both?