openpilot development flow
- We will develop on master, which is stripped and minified by CI and pushed to master-ci automatically if the tests pass. You probably should not be using master on devices.
- When we are ready to start the release process, we’ll push master-ci to devel-staging and open a pull request into devel. This pull request will be the spot for comments on the new release, and hotfixes at this point will be cherry picked from master into devel-staging. Once it’s good, we merge into devel.
- devel is built by CI, and pushes the built versions to release2-staging and dashcam-staging signed with the official comma release key.
- After the -staging branches are tested by the community for a few days, we’ll push them to release2 and dashcam.