A separate GitHub repository is created to manage each openIMIS component, e.g:
...
We use the Gitflow Workflow, which was first published in 2010 in a blog post from Vincent Driessen at nvie. We have extended this workflow to include country specific version of the component managed through the repository.
...
Using the Git branching features, each of these repositories will have a main branch (old master branch (- the latest stable version or production release) and a separate branch for each development phase.
...
As soon as a release is ready, it will be merged into the master main and will be tagged with a release number.
In case a bug has to be fixed quickly into the production release (master main branch), a hotfix branch is created. This branch is merged directly into the master main branch and into the develop branch. The master main branch will then be tagged with an updated version number.
After each official release and update of the master main branch, the new features/bug fixes will be integrated into the countries specific develop branches, adapted and tested against implementation's specific requirements before releasing for the country.
...
Naming convention will be established for branches and commits. Every commit should have an author and a short description. The naming and format conventions will be discussed during the Developers Workshop.
In addition with the generic version of openIMIS, one can have a country/implementation specific branches that are similar to the generic version. The naming convention for these branches is implementation/<name of implementation>/<name of branch | develop | main >
| Attachments | ||||
|---|---|---|---|---|
|