All contributions (PRs) to Sming Framework have to be done to develop branch. If a feature or bugfix is a major change please contact Sming team to prepare feature specific handling.
master: Branch that contains latest production (stable) release. No PRs other than Final Release updates will be merged into master. develop: Main development branch: contains all current new features.
This will mean that all contributors will have to submit a PR to a develop , it will be tested and then merged to develop for automated integration testing (via TravisCI, Jenkins or SemaphoreCI), as well as manual testing on a real device.
Sming Contributing flow:
- Fork Sming repo
- Create a branch off the develop: MyNewFeature
- Build, test your code
- Commit changes
- Push your changes to your fork on github
- Submit PR to the main Sming repo, develop branch.
- Work with other contributors to test your feature and get it merged to develop
This is the most common approach for a git-flow: http://nvie.com/posts/a-successful-git-branching-model/