Skip to content

Tags: zergey/bitex

Tags

1.2

Toggle 1.2's commit message
bumped version

1.1

Toggle 1.1's commit message
removed accidentally added file

1.0

Toggle 1.0's commit message
Merge branch 'dev' to bump master up to 1.0

0.7

Toggle 0.7's commit message
updated setup.py to new version(0.7)

0.6

Toggle 0.6's commit message
0.6 MERGED

0.5

Toggle 0.5's commit message
Snapshot of development to date (20 Jul 16);

Implemented REST apis, and at minimum public ticker, trades and order book funcs for them.
cleaned up API base class, and the respective folder;

From here on now, Vincent Driessen's branching model will be enforced, as described here:
http://nvie.com/posts/a-successful-git-branching-model/

TL;DR:
2 Undying branches: Master, Dev
3 types of supporting branches (feature branches, Release Branches, Hotfix branches) with
limited lifetime

- Features; Branch of from Dev, merge back into dev
- Releases: Branches off from dev, merges back into dev, master (naming conv: release-*)
- Hotfixes: Branches off from master, merges back into dev, master (naming conv: hotfix-*)

merge using --no-ff flags to keep history of these separate (more overhead, but better readability of history)