I think the state is useful because it provides a way to filter out tickets that are not immediately actionable (for example, there are several tickets that suggest schema migrations). When migrations land in core, we can then "accept" these tickets.
On Sunday, August 18, 2013 4:10:14 AM UTC-4, Wim Feijen wrote: > > Hi, > > When triaging tickets I came across the triage stage Someday/Maybe. The > docs say I shouldn't use it. :) I think they are right. > > For me triaging tickets is all about making a decision. I make a choice > between either: "yes, good idea", or "no, we definitely don't want that". > Someday/maybe seems like not a good choice here, because it leaves things > in the uncertain. > > Therefore, I'd like to propose to remove this triage stage, like we did > with design decision needed. > > Currently, there are 47 tickets marked as someday/maybe. Looking over > them, it seems to me that: > 1. most can be marked as Accepted. A solution may or may not be hard to > find but we accept that django could improve here. > 2. some should actually be marked as won't fix but weren't out of > hospitality. > > What is your opinion? > > Wim > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
