#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:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce):

 > I'm not opposed to re-adding some directives like .. _patch-review-
 checklist to try and preserve deep links people might have used, but I
 think it should be part of a documented policy. Why is this heading on
 this page important that it requires preserving?

 For example, https://docs.djangoproject.com/en/dev/internals/contributing
 /writing-code/submitting-patches/#patch-review-checklist has been on an
 automated welcome message on GitHub PRs for first time contributors for
 quite a while - so this link is used and shared quite extensively. I think
 it's normal to share a particular version of the docs in a link, but often
 in the internal docs, I share "dev" links so folks get the latest
 information on our processes - unfortunately these links are more
 "brittle".
 Setting a redirect would be great 👍

 This is not a documented policy. I'd say we change header names (though
 never really touched the Wiki). References we don't change very often and
 file renaming/removing is also quite rare.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35894#comment:8>
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/0107019306b9c2e4-a354fe72-af1f-43cc-8375-67e178e0e199-000000%40eu-central-1.amazonses.com.

Reply via email to