bradymiller wrote on Saturday, November 13, 2010:
hey,
The git conversion and git development work flow pipeline is pretty much done. I figured it would be useful to summarize the workflow (with applicable wiki links) here. The workflow is not set an stone, and is an attempt to get all the benefits from git while minimizing any harm to the main OpenEMR sourceforge git repository.
For more details on the actual git conversion, the wiki page for that is here:
http://www.openmedsoftware.org/wiki/Git_Migration
We recommend that all developers get acclimated to git, and we have posted a howto set up git for OpenEMR here:
http://www.openmedsoftware.org/wiki/Git_for_dummies
This tutorial will walk through all the tools needed to develop OpenEMR in git (setting up a repository, maintaining a repository, and submitting code for review or to commit to the main sourceforge git repository)
To minimize the risk of damage to the main OpenEMR git repository on sourceforge, we have introduced a commit work flow that is described here:
http://www.openmedsoftware.org/wiki/Repository_work_flow_structure
Please read through this to understand the workflow, and we will maintain the list of developers on this page. We have limited the actual sourceforge commit access to only a few developers (Integration Developers). We have also set up another group of developers, Privileged Developers, whom have the right to commit their code; however the actual commit will be done by an Integration Developer. So, when a Privileged Developer wants certain code committed, they simply follow these steps:
http://www.openmedsoftware.org/wiki/Git_for_dummies#Submit_your_code_for_commit_.28For_Privileged_Developers.29
I placed all the new repository documentation here:
http://www.openmedsoftware.org/wiki/Main_Page#Repository
I hope this is all clear and makes sense. Let the gitting begin.
-brady