#24989: Introduce contributor facing documentation for django.db.migrations
-----------------------------------+------------------------------------
Reporter: Markus Holtermann | Owner: (none)
Type: New feature | Status: new
Component: Documentation | Version: dev
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 Natalia Bidart):
Replying to [comment:5 HAMA Barhamou]:
> I think that this tiket should cover a broader need.
[https://forum.djangoproject.com/t/internal-organization-of-the-django-
project/18490]
Hey HAMA Barhamou, thank you for your interest in making Django better,
but please note that as mentioned in the first comment from Tim, this
ticket is intentionally scoped to only documenting the database migrations
machinery.
--
Ticket URL: <https://code.djangoproject.com/ticket/24989#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cd4bb14c8-57657106-cad0-4488-ad69-cf453a596b30-000000%40eu-central-1.amazonses.com.
