Execution Trace Team Work

###Team Management

Workflow

 issue 11 Find loops (AST) -->
      issue 16 Stack trace (Instrumentation)--> End Sprint 1.
         issue 20 Type trace --> 
            issue 17 Location trace -->
                 issue 18 Trace search. End Sprint 2.

Communication Policy

We must acknowledge every Slack message.

##Development Policies Nightly commits for personal branches.

Weekly commits (Mondays 9PM) for team branch.

#Delegation Sprint 2:

Integration (David in charge of Execution Trace branch).

Team Scheduling(Slack meetups Dana, commits Han).

Code Reviews (David and Dana, Han and Venkat).

Repository WorfFlow

#Initial Setup Clone the project's repository in your Cloud9 workspace. [How To](dana's wiki).

Create your branch.

   git branch branch_name

#Pull Before Pushing

Get up to date with the team branch.

   git pull origin ExecutionTrace
   git push origin your_branch

Pull a request to push your work

Do some work.

Commit your work.

   git add --all
   git commit --all (git commit -m "my commit message")
   git push --all origin your_branch	

Using the repository's Github page

  Add a pull request from your branch to the team branch. 
  Explain your changes.
  Commit to team branch by merge the pull request.

##Sprint 2 To-do list

    traverse tree
	find types
	instrument code
	add data to stack trace
	
    collect stack trace
	search by type, identifier, line