Do we need a milestone for the next version on core trac?

[johnbillion]

As we get toward the beta and RC stage of a release, there are many tickets on core trac that get bumped to the "Future Release" milestone.

Should we introduce a milestone for the next version after the current beta?

For example, while we're clearing out tickets for 3.9, I can see several tickets that would be good candidates for 4.0 but which end up going into "Future Release" and then in a few weeks time will probably get moved again into the 4.0 milestone, or possibly forgotten.

I'd see it as a new numeric milestone for each release (ie. 4.0, 4.1), not a persistent "Next release" milestone.

[johnbillion]

​Link to IRC discussion

We're going to try it out after beta 1 and the ticket numbers are down a bit. Need to avoid overloading the milestone with wishful thinking tickets (preferably only tickets with patches or actual intent to fix).

[nacin]

This is often done a bit before the release, but unless the release has already been branched, it often ends up becoming a cesspool of tickets by the time someone gets to work on them. It really depends on how well the current release is going in terms of allocation of resources (and by that I mean people).