Bad GitHub milestones

[pllim]

I see:

• v0.1.0 (way out of date)
• Future (too vague)

Both have issues assigned to them.

Desired outcome: Change the milestones to something that is correct and actionable. Remind the release manager to update the milestones every release (see astropy release procedures if you do not have one).

Thanks.

[hpparvi]

We now have a clear plan for the next stages of specreduce development, and the milestones have been fixed to reflect this plan. I will still need to attach the old issues to the new milestones, when appropriate, but I believe this issue can be closed now.