Source Code Management
We use GitHub as a source code platform for version control and publish Mata Elang to the public.
The various branches are used for Mata Elang development. The roles of each branches are described in the following table.
| Branch Name | Role | Derivation Source | Merge Target |
|---|---|---|---|
| master | A branch to put the released version. | ||
| develop | A branch to store the developing source code | master | release |
| release | A branch to put the version to be released next | develop | develop, master |
| feature-* | A branch to put the source code for the development of new features | develop | develop |
| bugfix-* | A branch to fix bugs of the developing version | develop | develop |
| hotfix-* | A branch to fix bugs of the released version | master | develop, master |
The following figure shows how branches work and the flow of branch control.
Source : https://nvie.com/posts/a-successful-git-branching-model/