Created by [ Rowan Dempster], last modified on Dec 27, 2019
In general, the master branch should be considered the only branch that will run in the car during the test track day. It should be considered a certified stable version of each module that will not break any dependent modules and should be updated before the code freeze on every development cycle.
The develop branch will be used as the branch that all feature development will be based off and contain all code that has been code reviewed.
Feature Development Process
Feature development should be performed by the following process
Release Process
The Manager should throughly test the develop branch of the entire
module and pipeline to ensure it works. This may involve scheduling a
Mini Test Track session, or at very least running rosbags through the
pipeline in the car itself. Once the Manager is satisfied with the state
of the develop branch, they will certify that it is stable and merge the
develop branch to the master branch. This should be done before the code
freeze.
Document generated by Confluence on Nov 19, 2021 12:21