Navigation Menu

Skip to content

Repository Structure

rzanoli edited this page Jun 6, 2014 · 18 revisions

The EOP source code is hosted on Github and managed using Git. The EOP GitHub repository consists of three main branches: the release branch is the branch containing the code that is supposed to be in a production-ready state, whereas the master branch is the main branch containing the code to be incorporated into the next release. The gh-pages branch contains the EOP web site.

EOP_Repository

Developers fork the EOP repository to create copy of it on the server (i.e. their server-side copy) and do pull requests to commit their contributions. When the source code in the master branch reaches a stable point and is ready to be released, all of the changes are merged back into release.

To quickly patch production releases EOP can use an additional branch namely maintenance branch. This branch, that is a temporary branch, is forked directly off of release. As soon as the fix is complete, it is merged into both release and master, and release is then tagged with an updated version number.

Maintenance

Clone this wiki locally