On 29/03/11 03:29, Julien Phalip wrote: > Hi, > > Since we've recently been discussing a few ways to improve Trac, I'm > suggesting to move the discussion which started a few minutes ago in > #5833 here so as not to pollute the ticket with too many meta > conversations. I'd also like to apologise for the confusion I seem to > have stirred by changing the milestone attribute of that ticket to > 1.4...
It was probably just as much my fault for changing it back, no need to apologise. I think we have been inconsistent with our use of this field, and my point in removing it was to make it clear that, despite what some people on that ticket no doubt believe, adding yourself as a CC to a ticket does nothing to make it happen, and neither does setting the milestone. Your e-mail makes me question the usefulness of the field too. One case it is useful when we near a release and there are some bugs that we need to get fixed. But perhaps that is overlapping with 'blocker' status. Another case is when we decide, as we did at least for 1.1 to 1.3, that certain features are going to get a lot of attention, including a core developer who commits to either developing or managing the feature into Django. Perhaps we should clear the milestone flags on all tickets, and add them only when a core developer commits to getting a ticket in. However, although a commitment from a core developer has usually been pretty meaningful, it is still possible that the feature won't arrive if it's simply not ready (I don't know what our record is like on this front - I suspect it has been pretty good, but not perfect). So what does the milestone flag actually tell you? The people developing the feature will know that they are doing so, and for other people looking on, the milestone flag may be taken as some kind of guarantee that it gets in. In reality, as Alan Kay said, "the best way to predict the future is to invent it", and maybe the lack of a milestone flag would actually encourage involvement. Thanks for opening the discussion, Luke -- If you can't answer a man's arguments, all is not lost; you can still call him vile names. (Elbert Hubbard) Luke Plant || http://lukeplant.me.uk/ -- 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.
