| Notewarning |
|---|
We know that we are moving to a distributed versioning tool. We haven't committed to Git (e.g., vs. Mercurial) at this time. |
The OpenMRS Developer Community is anticipating migrating to Gitdistributed versioning of our code. This page serves as a point of communication about the process.
Background
Distributed code versioning has become a more popular form of sharing code in place of the centralized model.
| Note |
|---|
Need to pull pros/cons, etc. from notes up here |
Requirements
- A clear understanding of how the new versioning system will effect our developers
- Branching
- Merging changes
- Submitting patches
- Releases
- A way (through APIs at code-hosting sites and/or conventions for repositories) for OpenMRS to find and organize existing repositories for the community's benefit
- Tutorials for developers to ease the transition
| Note |
|---|
Section incomplete |
Road Map
- Migrate HTML Form Entry Module to Git to get experience with using Git
| Note |
|---|
Section incomplete |
Links
- http://git.or.cz/course/svn.html maps maps SVN commands to Git commands
- http://blogs.atlassian.com/2011/10/confluence-git-rename-merge-oh-my/ Atlassian write up on moving from SVN to Git
- http://john.albin.net/git/cnovert-subversion-to-git
- http://nvie.com/posts/a-successful-git-branching-model
| Widget Connector | ||
|---|---|---|
|
| Widget Connector | ||
|---|---|---|
|
Notes from 2011 Implementers Meeting
Session: Migrating to Git/DVCS - Wednesday 11:00 11:17 - 12:30
Facilitator: ~bmamlinBurke Mamlin
Note taker: ~michaelMichael Downey
Timekeeper: ~mseatonMike Seaton
Pre-session questions:
- Do we want to change development models (i.e., distributed)?
- If we do, how do we get there?
...