Cut a first dev release

[patcon]

Since Agora is going to start using this, let's set some ground rules.

Let's follow semver:

How should I deal with revisions in the 0.y.z initial development phase?
The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

We'll start with v0.1.0.

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

We won't consider anything officially unbreakable (ie. we won't force ourselves to v1.0.0 if we break an API), but agora interfaces will only change in discussion with them.

I'll figure out pipy and manually push a release, though this should work from just a tag with pip, which I can document as well.

Todos

• merge Simplified clustering for Agora use-case #7
• create stub CHANGELOG.md Prepare for release v0.1.0 #18
• tag release v0.1.0
• PiPy packaging (no blocker)
  • update docs
  • settle on name Rename project/package #10
  • set up PiPy account
  • push first release

[patcon]

Done! https://pypi.org/project/red-dwarf-democracy/ (See #10 to see why desired name is a work-in-progress)