forked from project-chip/connectedhomeip
-
Notifications
You must be signed in to change notification settings - Fork 4
Development lifecycle
Vincent Coubard edited this page Feb 1, 2021
·
1 revision
This defines how we use branches in Mbed fork of CHIP.
- master is locked from local changes. It is updated at a regular interval (at least at the end of each Sprint) with code from upstream.
- Our pull requests are merged into the development branch. At the end of every Sprint a release is created out of the development branch and at the beginning of every Sprint, the development branch is rebased against the master branch to keep it in sync with upstream.
- To verify that we are not breaking anything; CI workflow from upstream are run in this repository.
- Feature development happens in dedicated feature branch to isolate the feature from external changes while its being developed.