-
Notifications
You must be signed in to change notification settings - Fork 221
Development Process
jtlan edited this page Sep 18, 2015
·
8 revisions
- Pull latest develop
- Create a branch off of develop, usually named after the ticket (ex: "
1791fix1
", "1684ER
", etc). - Work and commit on branch.
- Be sure to write a test for your new feature or the bug you fixed!
- Push branch to remote.
- Create a pull request from your branch into develop.
- Assign a developer to review (probably one of @jtlan or @bluong).
- If you receive a [-1], back to step 3 to address concerns.
- Pull latest develop.
- Create a feature branch off of develop.
- Follow steps 2 through 8 above, but cutting off and merging into your feature branch instead of **develop. Tag any pull requests with the [Side Branch] tag.
2015-09-18
We're still looking into this issue, but our setup doesn't appear to work correctly with newer versions of Node. Use v0.12.7
until we can get to the bottom of this.