On a broader note, how does the deployment pipeline for documentation work? It seems to me that for branches that are in pre-release (3.10) or active development (3.11), the documentation should be continuously deployed, while deployment of changes to earlier documentation should follow minor releases for those versions.

Sorry this question is naive -- I don't know how it works currently. Would it be possible to set something like this up?

On Thu, Aug 12, 2021, 3:02 AM Serhiy Storchaka <storchaka@gmail.com> wrote:

11.08.21 21:35, Brett Cannon пише:
> So my question is whether we want to push to be more diligent about
> updating What's New by b1 so people can provide feedback during the
> betas beyond just reporting breaking changes?

I think that What's New should be updated as soon as possible,
immediately after the addition of the feature. I started contributing to
Python after reading What's New for one of early alphas of 3.3 (and the
questioned feature was changed later). There were other examples, when
features were advertised in alphas, but were changed after getting a
feedback before betas.

_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/RQQ2QEV3OKCMAJGHLB52SKXLAIL7BB34/
Code of Conduct: http://python.org/psf/codeofconduct/