PySCeS releases

For any future releases, I propose the following general sequence of events.

• Finalise source (merge "development" branch, update version numbers, dates, dependencies etc.)
• Finalise documentation (update module)
• Announce codebase freeze (no new code, only release bugfixes)
• Test builds on difference OS's, Python releases etc.
• Freeze codebase
  • Create GitHub release with final version tag (new releases will be x.y.0 with interim releases x.y.z no post1, a, etc)
  • Create PyPI source bundle
  • Upload PyPI source bundle (create PyPI release)
  • Create/upload PyPI binaries
  • Create/upload Anaconda binaries
  • Create "development" branch for future development
• Announce codebase unfreeze
• Update RTD
• Update website