#21070: Clarify document DATABASES change
--------------------------------------+------------------------------------
Reporter: joejasinski | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by joejasinski):
I'd be glad to take a stab at starting such a new page and submitting for
review, if desired. Where would be a good place in the doc codebase to
place such a page? In the ideal layout, would the API docs remain mostly
as is (with the addition of a link to the new section) or should the new
section include the available DATABASES keys as well as some prose and
examples?
--
Ticket URL: <https://code.djangoproject.com/ticket/21070#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.77b6e59c5a81cbd720880e1b3973d3b9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
