On Aug 12, 2021, at 12:58, Jack DeVries <jdevries3133@gmail.com> wrote:
If you look at the version picker on docs.python.org you will see that we already have the docs for 3.10 and 3.11 available. I don't know if they are updated per release right now or per commit.
I understand that they are available options. To clarify my suggestion, I think that 3.11 should be updated on a per commit basis (continuous deployment); including updating the what's new pages continuously. If that is not done already, I'm curious if it is been looked into before, and whether it might be possible to set things up like this?
This is mainly from memory so some of the details may be incorrect but it's pretty close. The Python docs on python.org come in various formats - on-line HTML and various downloadable formats - and in English as well as various translated versions. It takes multiple hours on a dedicated virtual server to build the complete set of doc products, so updates are done on different cycles. The complete set of document products in all languages for branches either in feature development (currently 3.11), pre-release (3.10), or bugfix (3.9) status, are built and published every 24 hours. In addition, the on-line English html versions for these branches are re-built and published every 3 hours. Docs for security-fix branches (3.8, 3.7, 3.6) are generally only re-built when new releases are made. We also produce archived copies of the documentation current as of each release (https://www.python.org/doc/versions/). Julien Palard is the release team documentation expert who manages the doc build and translation processes, along with the PSF IT team headed by Ee Durbin. There is some information (not quite up-to-date) in the Dev Guide. The infrastructure code is primarily in https://github.com/python/docsbuild-scripts and https://github.com/python/psf-salt. -- Ned Deily nad@python.org -- []