On Tue, Sep 20, 2011 at 10:16 AM, Carl Meyer <c...@oddbird.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > The milestone field came up again in IRC discussion tonight between > Julien and Paul and I -- namely, that it doesn't seem all that useful > and causes noise in Trac. > > It might have made sense back when we had more feature-driven releases > and a feature voting process, but as we're (trying to) move towards > date-based releases and we've moved away from feature voting, I don't > see what purpose it serves. Tickets marked "release blocker" must get > fixed before release, any other accepted ticket is always a candidate to > get fixed if someone works on it in time. Milestone doesn't add anything > but noise. > > > Julien already raised this topic a while back [1] and Luke more or less > agreed. Can we just go ahead and remove the field, or does somebody want > to present an impassioned defense of its usefulness (in which case you > should explain what it means, which tickets should get a milestone set, > who should set it, and under what conditions it should be removed or > bumped)?
I agree that it's adding more noise and confusion than it's worth. Kill it with fire. The only use case for Milestone that I can think of is to track backwards incompatible changes that need to be revisited for when we get to v2.0. However, I think those could be handled just as elegantly with the someday/maybe ticket state. Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
