#35894: Move away from the term "patch" to refer to a contribution/pull request
in
the contributor documentation
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: Baptiste
Type: | Mispelon
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Baptiste Mispelon):
* needs_better_patch: 1 => 0
Comment:
I've updated the PR after some reviews, here's the current summary:
* "patch" is replaced with a mixture of "pull request", "change" or
"contribution" on all the pages that talk about contributing to Django
(this matches the current effective practice and is similar to what was
done on the Python devguide)
* The word "patch" is kept when talking about an actual patch file
* The word "patch" is kept in the names of some files and in some anchors,
so as not to break existing links
There are also two PRs connected to this ticket:
* One for Trac itself to rename the fields on the UI (the name of the
field is not affected, so things like report links will continue to work):
https://github.com/django/code.djangoproject.com/pull/224
* One for the dashboard to rename some of the metrics:
https://github.com/django/djangoproject.com/pull/1729
While these two PRs are related, they don't technically require to be
merged/deployed in any specific order. I personally suggest waiting until
the docs change in this ticket are live before deploying them.
--
Ticket URL: <https://code.djangoproject.com/ticket/35894#comment:11>
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/010701931b436916-6fdad3fc-644a-4d90-a5c5-2b5ae3076978-000000%40eu-central-1.amazonses.com.
