We should write down the steps to properly running a rebuild, e.g. on release day or for end-of-life versions. I ran the rebuild on Monday to ensure that /3/ was promptly updated, but there was no process to follow.

Likewise, for versions that become unsupported, we should trigger one final rebuild so that the "outdated" header/warning is added. For example, we need to do this now with https://docs.python.org/3.8/.

cc @JulienPalard -- I'm not sure how you've handled this in the past (especially EOL versions), and if there is a process you would recommend?

A