Next Release Milestone

[CalebLarsen]

First off, congratulations on the release! Lots of big changes and writing and merging tree-house was huge.

One of the aspects of the project I enjoyed approaching the release was the milestone with associated issues. I liked seeing what the goals were and what issues were pressing. It was also helpful in determining what issues to try and pick up (though @the-mikedavis often came in with a better solution haha)

Is there interest in maintaining the Next Release milestone? From what I've read, I believe it needs write access so it would have to be a maintainer. I understand that I'm basically asking for extra bookkeeping to be done, so if there isn't interest, that's ok.

Anyways, congrats again! Thanks for making helix what it is!

[the-mikedavis]

We've used milestones in the past as an easy way to track a handful of issues or PRs that we want to be able to look up quickly. Typically I'll make one a few weeks before the release to track bugs that I want to see squashed before the release. So it's more like a pre-release wishlist of fixes.

I'm not really interested in using a milestone to track everything that could/will end up in the next release. It's a fair amount of work to curate that and I don't think that rigorous project management styles fit well for a project like this which is done in free time. A PR is added to the next release when it's ready and reviewed and both of those things are unpredictable because scheduling free time is unpredictable.