Opened 10 years ago
Last modified 14 months ago
#24989 new New feature
Introduce contributor facing documentation for django.db.migrations — at Version 2
| Reported by: | Markus Holtermann | Owned by: | Markus Holtermann |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | |||
Description (last modified by ) ¶
It would be helpful for new contributors as well as for other core devs not involved in certain parts of Django, to have documentation that outlines how these components work. Tim proposed to add that documentation to docs/internals/. I'd put it into docs/internals/api/
E.g. in migrations: you have a ModelState and to detect changes the autodetector takes all migrations and build the final model representation and then compares this ProjectState to the ProjectState constructed from all currently available models.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR].
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Description: | modified (diff) |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
| Summary: | Introduce low-level documentation on Django's components → Introduce contributor facing documentation for django.db.migrations |
| Triage Stage: | Unreviewed → Accepted |
Note:
See TracTickets
for help on using tickets.
I think the idea is accepted, but a ticket is needed for each thing you want to document, not all of them in one ticket. Do you want to retitle this one to cover migrations?