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
No edit summary
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 Git =


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 [http://git.or.cz Git]. A [http://moodle.org/mod/forum/discuss.php?d=99763 discussion] is taking place in moodle.org forums about a possible move to Git.
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 [http://git.or.cz Git]. A [http://moodle.org/mod/forum/discuss.php?d=99763 discussion] is taking place in moodle.org forums about a possible move to Git and contains a lot of information.


Some other systems have been mentioned, such as [http://www.selenic.com/mercurial/wiki/ Mercurial].
Some other systems have also been mentioned, such as [http://www.selenic.com/mercurial/wiki/ Mercurial].


= Moving to Git =
= Git and human usage =


== Blocker ==
* A lot of people need an easy interface to the revision system.  Most of them are currently using TortoiseCVS (a lot of translators, it seems). There is no tool (as of late June 2008) for Git that is equivalent in ease of use to TortoiseCVS, though [http://digilander.libero.it/mcostalba/ qgit] and [http://cola.tuxfamily.org/ git-cola] are improving. In the meantime, people could use a CVS gateway, which would need to work both ways (read & write), to give people time to change over once proper tools become available.
* Developers using Eclipse need to wait for a plugin. There is a [http://wiki.eclipse.org/EGit/Proposal proposal], but it's still not ready for prime time (June 2008).
* [http://vim.sourceforge.net/scripts/script.php?script_id=90 VCSCommand] plugin for Vim now supports Git.
* Some users are using CVS mirrors to deploy (and update) their site. Can't break this. A read-only CVS gateway could be a good working solution to this.


Jira support: there is a [http://jira.atlassian.com/browse/FE-337 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.
= Git and server-side tool integration =


== Problem that might be solved by a CVS gateway ==
* Web interface to the repository: Git provides a web interface. Alternatively, Trac now provides a [http://trac-hacks.org/wiki/GitPlugin GitPlugin] that could be used.
* 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;
* Bug tracking: see [http://forums.atlassian.com/thread.jspa?threadID=24671&tstart=0] and [http://jira.atlassian.com/browse/FE-337] (support still uncomplete, on June 24 2008).  Martín Langhoff says: "[http://moodle.org/mod/forum/discuss.php?d=99763#p441057 looks like there is a mercurial plugin we can quickly grab and, ahem, repurpose...]". We could also use a CVS gateway, though there could be problems with this workaround, as "[http://moodle.org/mod/forum/discuss.php?d=99763#p440831 the rev numbers don't line up]".
* 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 [http://wiki.eclipse.org/EGit/Proposal proposal] to create an Eclipse integration plug-in (unresolved)
 
== 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?

Revision as of 06:29, 24 June 2008

Proposal to move Moodle development from CVS to Git

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 and contains a lot of information.

Some other systems have also been mentioned, such as Mercurial.

Git and human usage

  • A lot of people need an easy interface to the revision system. Most of them are currently using TortoiseCVS (a lot of translators, it seems). There is no tool (as of late June 2008) for Git that is equivalent in ease of use to TortoiseCVS, though qgit and git-cola are improving. In the meantime, people could use a CVS gateway, which would need to work both ways (read & write), to give people time to change over once proper tools become available.
  • Developers using Eclipse need to wait for a plugin. There is a proposal, but it's still not ready for prime time (June 2008).
  • VCSCommand plugin for Vim now supports Git.
  • Some users are using CVS mirrors to deploy (and update) their site. Can't break this. A read-only CVS gateway could be a good working solution to this.

Git and server-side tool integration