> 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?
I was originally thinking that 3.10 documentation should be deployed continuously as well, but on further thought I realized that that would put the beta releases out of sync with the documentation which obviously does not make any sense. Maybe we could add a new tab to the version picker called 3.10/HEAD or similar. Maybe there's another solution?
Either way, continuous deployment of documentation for 3.11 (or whatever version cpython/HEAD is at any given time) seems like it should be the norm if it isn't already. If that is already the case, I'm sorry for the noise! I still think that continuous deployment of documentation on the head of the beta or alpha release branches is worth considering, maybe with a different label on docs.python.org like "cpython/3.10@latest" or similar.