Workflow

• Issue is opened
• Assignee creates branch from master called task###_DESCRIPTIVETAG
• Make system compiles branch and populates all unversioned objects in /output_local
• Assignee performs work, frequently committing to branch and frequently updating branch from master
• Commits to branch must have a short description
• Assignee maintains issue comments
• Comments at least once on any day in which meaningful work is done
• Comments at least once a week on any open issue even if no work is done
• At any point someone reading the issue comments should know the status of the task
• Assignee completes work
• Assignee issues pull request
• Peer reviewer comments on pull request via github
• Assignee addresses peer review comments
• Assignee completes pull request
• Commit to master should have a longer description
• Assignee uses make system to compile master
• Assignee debugs compile and commits results
• Assignee deletes branch
• In some cases we can leave stale branch persistent if we want revision history of branch to stick around for a while; then we just need a clean-up process for branches
• Any time any output is made public (e.g. someone gives a talk or we post a draft or submit to a journal) we consider that a “release.” We tag the state of the repository at that point and give it a “release” name associated with the output (e.g., nov2016draft).