#10236: Change order of actions in syncdb
---------------------------------------------+------------------------------
          Reporter:  jbergstroem             |         Owner:  nobody           
     
            Status:  new                     |     Milestone:                   
     
         Component:  Core framework          |       Version:  SVN              
     
        Resolution:                          |      Keywords:  order syncdb sql 
index
             Stage:  Design decision needed  |     Has_patch:  1                
     
        Needs_docs:  0                       |   Needs_tests:  0                
     
Needs_better_patch:  0                       |  
---------------------------------------------+------------------------------
Comment (by russellm):

 Replying to [comment:4 toxik]:
 > Replying to [comment:3 ubernostrum]:
 > > This isn't "ready for checkin"; there's been no review of the patch
 whatsoever, and no feedback from the dev team on whether this change will
 be accepted.
 >
 > I was under the impression that the triaging was exactly for that
 purpose: flagging 'I reviewed this.' And I did.

 If you follow the
 [http://docs.djangoproject.com/en/dev/internals/contributing/#triage-by-
 the-general-community triage notes] the jump from 'Unreviewed' to
 'Accepted' is only for obvious or trivial bugs. This isn't an obvious bug,
 and it won't be a trivial change - it has consequences for existing code.
 As a result, a design decision is required.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10236#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to