...
Instead of a single master branch, this workflow uses two branches to record the history of the project. The master branch stores the official release history, and the develop branch serves as an integration branch for features:
Mentioned above means that development happens in two separate directions: master and development. Master could be also called production and development as a testing branch. Branch respectively means the independent clone (copies) of code (for a user it just means the program or client-software).
Master branch serves as a working software (or code). This branch stores adjustments only tested and approved by customer and sometimes is delivered only in releases if that is required.
Development branch is used for development purposes: this is a place where all new features and fixes appear first. After successful testing and approval, code is cloned (copied) from develop to master brach.
Note that if a bug appears in the development branch, the production is not influenced by that. So mentioned approach minimizes the risks and costs of unsuccessful implementation of a feature as this feature can be repeatedly be adjusted until it is right and only then merged to the master code.
...
So for example if there are 3 parallel issues being developed by us and you accept only first of them as finished, you can go live with it and we can keep working on the rest of them and realease them one by one once you are sure they are ready for live.:
| Note |
|---|
Please make sure you are deploying the right code to the right system |
Please note that use of GIT repository allows minimizing costs of unsuccessful implementation even in master code: it allows reverting the code to any previous versions, allowing to revert incorrect changes (so production is back to a working state) if some issues are discovered only in production.
...