These are steps to get rid of the stable branch

Thanks to Travis CI and the unit tests, the master branch is almost
always of sufficient quality to be used.

Other pros:

* Wiki content matches the default branch.
* Project stats at Github are up to date.
* Less merge overhead at release time.

CONTRIBUTING.md

@@ -5,10 +5,6 @@ smoothly into topydo.
 
 ### General
 
-* This Github page defaults to the **stable** branch which is for **bug fixes
-  only**. If you would like to add a new feature, make sure to make a Pull
-  Request on the `master` branch.
-
 * Use descriptive commit messages. The post
   [How to write a commit message](http://chris.beams.io/posts/git-commit/) by
   Chris Beams has some good guidelines.

README.md

@@ -43,6 +43,6 @@ Demo
 [2]: https://github.com/ginatrapani/todo.txt-cli
 [3]: https://github.com/bram85/todo.txt-tools
 [4]: https://github.com/bram85/topydo/wiki
-[5]: https://raw.githubusercontent.com/bram85/topydo/stable/doc/topydo.gif
+[5]: https://raw.githubusercontent.com/bram85/topydo/master/doc/topydo.gif
 [6]: https://github.com/jonathanslenders/python-prompt-toolkit
 [7]: https://github.com/collective/icalendar