#36665: Rewrite reference to model manager usage to avoid saying "tricky"
-------------------------------------+-------------------------------------
     Reporter:  Jacob Walls          |                    Owner:  (none)
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):

 Super, thanks for confirming.

 > we tend to use "Documentation" for tickets around the process of
 building/handling docs, not the doc content itself.

 You bring up a long-time point of confusion for me. Elsewhere like the
 [https://code.djangoproject.com/wiki/Reports Trac reports], it's implied
 that the documentation component includes doc content, e.g. "Documentation
 patches that need review" or "Documentation tickets that need patches". I
 wouldn't expect those to only link to sphinx/infra related tickets.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36665#comment:3>
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 view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070199e44a15b8-10e3707e-9bf3-4f80-bd64-27a9761a2e34-000000%40eu-central-1.amazonses.com.

Reply via email to