[wp-meta] [Making WordPress.org] #387: Do we need a milestone for the next version on core trac?

Making WordPress.org noreply at wordpress.org
Wed Mar 5 21:42:10 UTC 2014


#387: Do we need a milestone for the next version on core trac?
-------------------------+------------------
Reporter:  johnbillion   |      Owner:
    Type:  enhancement   |     Status:  new
Priority:  normal        |  Component:  Trac
Keywords:  dev-feedback  |
-------------------------+------------------
 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.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/387>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list