Quote:
Originally Posted by notmattlythgoe
The thing we're struggling with right now is when to branch, when to tag, etc. We just haven't figured out the best process for us yet. What do you guys do?
|
Typically, everything lives in master. Sometimes we will tag at the end of an event so we can dial the comp bot back to where it was (as we change code a lot between events), but most times we forget to do this. Usually there is only a small group of developers using one laptop to write code, so keeping branches in sync isn't really an issue.
If a student is working on a feature that is easy to break off, I will have them make a branch that we can pull in later. An example of this is something like a tiny HTTP server or your vision code. Define the interface then let them hack on the implementation in a branch.
The main rule is don't commit code that breaks the build!