On Tue, Nov 4, 2008 at 2:58 AM, Bob <[EMAIL PROTECTED]> wrote: > On a somewhat related note, is there some reason that 1.0.1 and 1.1 > milestones have not been created in Trac? It seems like triaging bugs > into one of these releases should happen in Trac, not the mailing > list.
Yes, there is a reason, and it has been given several times in recent history. The v1.0.1 milestone has not bee created in Trac because it will not in any way help us deliver the v1.0.1 release. There is no difference between the "list of all bugs' and the "list of bugs that we want to close for v1.0.1". We may not be successful in meeting this goal, but that doesn't change the underlying goal. In understand that twiddling milestone flags on tickets apparently gives some people the warm, satisfying feeling that they are helping. However, speaking as one of the core developers, it would be much more helpful for that effort to be directed towards actually triaging new tickets (validating that a bug exists, finding duplicates, correctly classifying tickets etc), writing patches, and testing those patches. These are the jobs that are hard to do, and aren't assisted by having a new milestone flag to fiddle with in Trac. The 1.1 milestone doesn't exist because we haven't decided what will be in v1.1 yet. Once the discussion period is over (in a week or so), the milestone will be opened, and tickets will be assigned. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
