Can we change milestones so they're not always out of date?

Are people OK with changing our milestones from current++, 3.0, and future to just “ASAP” and “Future”? I think that’s pretty much how we’re using them.

We’ve released 2.22, but our docs repo has 2.19++ as the most recent milestone I can apply and RStan has 2.15.

3 Likes

That looks very reasonable to me.

That sounds good to me. I’m assuming we still close milestones as we hit releases?