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

Development:Git Migration Workflows

From MoodleDocs
Revision as of 11:44, 26 October 2009 by David Mudrak (talk | contribs) (Undoing all my recent work - it is at a separate page)

Workflows for Migrating to Git

Quite a number of developers are now familiar with git and are enthusiastic about the power and flexibility it brings to the development process. It is not clear how workflows in the current development process will transfer if a switch to git is made.

Git doesn't place constraints to one model of development which is both a feature and a hindrance for people understanding how the development process takes place. A number of workflows need to be developed in order that developers can understand how git would fit into moodle development.

Please edit this page to add your suggested workflows or questions for a workflow to do something.

General Model for Commiting to HEAD

Summary: How do developers 'commit' to the canonical repository?

  • Developers 'push' to a central repository as happens with CVS now. Commit access is granted via ssh. (But external contributors can publish their git repository branches to developers with commit access for inclusion to the mainline)
  • Developers push to their personal repository and an integrator/gatekeeper approves and merges changes (e.g. linus kernel branch)
  • Others/hybrid approaches?

Commiting to STABLE branches

Summary: How do developers commit to the stable branches? How do we ensure changes have been merged into head?

Retrieved from "https://docs.moodle.org/33/en/index.php?title=Development:Git_Migration_Workflows&oldid=64685"
Powered by MediaWiki