Create release roadmap

[athowes]

With v1.0.0 approaching I suggest we update our issue tagging away from "before next release" or "in future" toward something giving a more concrete idea of when issues are to be addressed by which release.

[athowes]

Post release meeting, invite others.

[kgostic]

Should this be closed as completed?

[athowes]

Closing as stale / incomplete. In November I think we agreed on a list of issues (tagged as public release) to do before public release in December.

[seabbs]

I still plan to do this for development going forward

[athowes]

When you're next working on this @seabbs I'd be keen for:

• Remove "low, medium, high" from everything
• Re-specify which issues are to be done before pubilc release
• Assign and wrap those
• Make public release
• Start with more mature development cycle