I want to start a hacking guide on the wiki. First and foremost I'd like to be able to give some sensible direction about where to branch new features and/or bug fixes from.

Currently it looks like 'dev' branch has been forgotten and all changes are being merged into master. I'm comfortable using master as a development branch, but we should have an alternative live/stable branch in that case, so that bugfixes can be branched off without pulling in lots of experimental and possibly API breaking fixes.

What we're doing for distributed-process-platform is

• master = stable/live, bugfixes branch from here
• development = next-release, features branch from here

I realise there's a bit more overhead in maintaining an additional stable branch, but personally I think it's worth it. We could, of course, leave this change until after our next release to hackage, giving us a bit of breathing space to stabilize everything.

I'd also like to set up some milestones on the issue tracker, without specifying any dates. This gives us a chance to collaborate around which bugs/features go into the next planned release and gives users at least a vague sense of our roadmap.