#22603: Reorganize code in django.db.backends
-------------------------------------+-------------------------------------
     Reporter:  aaugustin            |                    Owner:  gchp
         Type:                       |                   Status:  assigned
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  1.8-alpha            |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by timgraham):

 There are still a couple large patches that touch these classes that may
 make it into 1.8 (in particular,
 [https://github.com/django/django/pull/3669 PR 3669]), so let's hold off a
 bit longer on this -- I'm thinking after the "feature freeze" on Monday,
 but before we cut the branch and issue an alpha release.

--
Ticket URL: <https://code.djangoproject.com/ticket/22603#comment:9>
Django <https://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 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.72f2532ad3d4ace128873d98ff8f25ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to