Each sprint will have two branches in the GitHub repository
- Sprint branch which is staring point of the sprint
- This branch represent where a sprint has been started and affords ability to cleanly rebuild another staging branch in the case it is required. For instance, it might be required by failed integration of features or unaccepted features by VIVO leadership group.
- This branch after its creation from the main repository branch might have a PR from a feature lead. A feature lead is the owner of the main idea for a feature which should be developed during the sprint, or a person with the highest expertise for that feature in the sprint team. The PR should define main frame for the feature implementation, or represent implementation of proof-of-concept with the goal to make the sprint feature implementation smoothly. The PR will be reviewed and merged by VIVO core team members.
- Sprint staging branch which all feature branches submit PR to, i.e. this branch should ensure feature integration during the sprint. It might be also used for infrastructure deployment for demonstration purposes (to VIVO leadership group or interested VIVO customers). The staging branch upon approval of features should then submit PR to head in which should undergo another high level review by committer team.
