anchor.diff:    * Revisions contain bugfixes only.
   
   We don't do alpha/beta releases, because if people want to try out the latest
  -thing, they can just use +develop+.
  +thing, they can just use +master+.  We expect most people to do this.
  +
  +
  +
  +Code Quality
  +------------
  +
  +Since people will often pull directly from +master+, +master+ must always be in
  +a releasable state.  This means anything going into +master+ must:
  +
  +* Work as intended.
  +
  +* Be documented (both in source code comments, and in the user-facing
  +  documentation).
  +
  +* Have major new changes and/or functionality covered by unit tests, which are
  +  runnable through +test.py+.
  +
  +In short: if you can't show a test proving it works, it doesn't work.
   
   
   
  
positive.code: 
  
  
  Branches
  --------
  
  We use http://nvie.com/posts/a-successful-git-branching-model/[git-flow] for
  handling branches and releases.  This means:
  
    * +master+ holds the latest stable release.
    * +develop+ holds the current, possibly-broken development version.
    * +feature/*+ branches are for new-feature development (and always get merged
      into +develop+)
  
  
  
  Version Numbers
  ---------------
  
  For the most part, homectl's version numbers don't matter -- most people can use
  the +master+ branch and be happy.  Different versions exist only to mark
  particularly stable points during development.
  
  Versions are named using the standard <major>.<minor>.<revision> scheme:
  
  
negative.code: 
  .Don't Repeat Yourself.
  
  Enough said.
  
  .Don't assume anything about the environment.
  
  