Github issues do not have the ability for anyone to close, tag, or create milestones. You have to be the creator of the ticket or someone with commit access. Django's track instance allows anyone to participate in this way and is one of the major reasons to my knowledge that Django will keep it's trace instance.
On Wednesday, April 18, 2012 at 7:39 PM, Łukasz Rekucki wrote: > On 19 April 2012 00:55, Donald Stufft <[email protected] > (mailto:[email protected])> wrote: > > Github Issues are not flexible enough for Django. > > > That's rather a vague statement. Github issues are actually more > *flexible* then Trac as you can define any set of tags for an issue. > What Django could possibly want to have is a way to create extra > constraints on the tags, but as a matter of fact, the current Trac > instance doesn't do that! (you can have an issue with "tests needed" > but without "patch needs improvement"). > > -- > Łukasz Rekucki > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. 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.
