From 9ef77025d3fa2ec81e5d0a23a57e007ef70be7ca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miguel=20C=C3=A1rdenas?= <78029302+miguelcsx@users.noreply.github.com> Date: Wed, 18 Sep 2024 22:39:04 -0500 Subject: [PATCH] Clarify the documentation update process (#1395) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- documentation/devguide.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/documentation/devguide.rst b/documentation/devguide.rst index a17ed342a9..7c53d054e1 100644 --- a/documentation/devguide.rst +++ b/documentation/devguide.rst @@ -19,10 +19,12 @@ main Python documentation, except for some small differences. The source lives in a `separate repository`_ and bug reports should be submitted to the `devguide GitHub tracker`_. -Our devguide workflow uses continuous integration and deployment so changes to -the devguide are normally published when the pull request is merged. Changes -to CPython documentation follow the workflow of a CPython release and are -published in the release. +Changes to the Developer's Guide are published when pull requests are merged. + +Changes to the Python documentation are published regularly, +ususally within 48 hours of the change being committed. +The documentation is also `published for each release `_, +which may also be used by redistributors. Developer's Guide workflow