Milestones are documented in CONTRIBUTING

[benoitbryon]

As maintainers of django-doctor, we have to triage and priorize tickets. What about using Github's milestones?
Here is a proposal:

• create a milestone for each release, so that milestones and CHANGES are consistent.
• maintain wishlist using 3 milestones like this https://github.com/python-hospital/hospital/milestones. They allow us to distinguish "must have" and "nice to have" features. We will try to address "must have" first. But we won't block pull requests about low priority features.

This behaviour is a first simple step to orchestrate development process. Later, we may setup third-party services like huboard or waffle.io. Could be other tickets. My initial motivation here is to triage the tickets I am about to create ;)

Except otherwise specified, I will create these milestones and start using them. Then I will refactor milestones and move issues depending on comments...
This ticket will be closed when milestones workflow gets quite stable and is documented in some CONTRIBUTING file.

[benoitbryon]

Note: if you know a third-party reference that explains a well-known and suitable workflow, let's paste the link here. I think we'd better use an existing third-party convention (provided it fits our needs) than maintain yet another one.