I agree with what Russ and Tim said. -0
On 19 August 2013 02:36, Russell Keith-Magee <[email protected]>wrote: > > On Sun, Aug 18, 2013 at 4:10 PM, Wim Feijen <[email protected]> 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? >> > > I'm not sure I agree. > > DDN was being variously used as "accepted, but we need to work on the > design" and "don't know if we want to accept this". This meant it ended up > being an area where we punted on making hard decisions. > > However, "Someday/Maybe" are ideas that have been accepted, but are > dependent on large pieces of work (like schema migrations or composite > keys), or large backwards incompatibilities. If the dependencies land, or > someone can work out a way around the backwards incompatibility problem, > then they could move back to "accepted". > > Yes, we could just mark these all as "accepted". However, IMHO the > "Someday/Maybe" marker provides a useful indicator to the community -- that > this feature isn't going to land any time soon. Look at any long term > accepted ticket, and there will be a "when will this be fixed in trunk" > comment; "Someday/Maybe" gives a pre-emptive answer to this question. > > I'm -0 to removing Someday/Maybe. > > If there are tickets in Someday/Maybe that should be marked wont fix, or > should be in accepted (because there's no architectural reason that they > couldn't be implemented right now), please call them out -- it's entirely > possible there are some tickets in there that need to be reassessed. > > Yours, > Russ Magee %-) > > -- > 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. > -- 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.
