HOW-TO-RELEASE

The process for pushing a new version is too complicated and
manual. 


* Update HISTORY
* Do the THINGS TO CHECK BEFORE DEPLOYING (below)
* Run configuration tests (HOW-TO-CONFIGURATION-TEST
  with midje-version set to a non-snapshot value.
  (Note that this uploads.)

* DO NOT CLEAN.
* Use bin/update-project-files and bin/version to set the examples
  appropriately. For example:
      bin/update-project-files 1.3.0
      bin/version 1.3.0 1.2.1 1.2.0
* bin/gather-downloads
* Update README.md (including version number)
* Commit
* git tag -a -m "message" v.x.x.x   ;; git push --tags
* Push to github

* Update example page, if needed.
* Try out downloads.


THINGS TO CHECK BEFORE DEPLOYING:
* uncomment the `:warn-on-reflection true` line in project.clj, and run `lein midje`
  to check for any reflection warning inadvertently added. (there will be warnings from
  libraries we use that we cannot remove)
  
* Check for any public vars that shouldn't be visible to users. Hide them.
  (map str (vals (ns-publics 'midje.sweet))) 
  (pp)