Repository navigation
Retire/symlink EOL versions? #298
Description
Activity
I don't remember moving builds to the release folder, and it looks like your
lsshows that Larry did.Anyway, we should be carefull to not break something, I mean if https://docs.python.org/release/2.0.1/ worked it have to work: let's not create 404s.
To keep things as simple as possible we could just replace current symlinks with simple copies.
Next question would be: could (or should?) docsbuild-script automatically archive builds in
release/?I don't know how useufll this folder is.
I don't remember moving builds to the release folder, and it looks like your ls shows that Larry did.
@larryhastings do you recall what you did here? Looks like it was in 2020, though, so a while ago!
Anyway, we should be carefull to not break something, I mean if docs.python.org/release/2.0.1 worked it have to work: let's not create 404s.
To keep things as simple as possible we could just replace current symlinks with simple copies.
Indeed, my proposal is not to change any of the
release/links, but instead to delete the symlink e.g./3.6/to/release/3.6.15, meaning that it is 'retired' from docsbuild-scripts, and just kept as a simple static archive, with no further rebuilds. The question is how best to ensure that we keep the EOL banner, etc.From #294:
[Hugo]
Do we need to rebuilt EOL versions at all?[Julien]
It's always a good idea to be able to do so:- To add the EOL banner (once).
- To update the sidebar maybe.
- To update any other thing that we would need to update like meta tags, or I don't know.
I think for EOL versions that are still in
/srv/docs.python.org/, we should ensure we can rebuild them. As shown though (#294, #295), this is increasingly tricky, especially before 3.8 when therequirements.txtfile was introduced.My preference for EOL versions would be to remove the switchers (which will become out of date) and instead use the banner and sidebar to redirect people to current stable. Those that still need to use EOL documentation will (I presume) use direct links. There is some precedent for this, as e.g. the 3.4 documentation has no switchers.
A
Currently, 3.0-3.5 and 2.0-2.6 are symlinked to the
release/directory. Should we also retire 2.7, 3.6, 3.7, and 3.8 in the same way?I'm not sure what procedure @JulienPalard has used in the past, as https://docs.python.org/3.5/ shows the EOL banner even though it is symlinked, meaning the files in
release/3.5.10have changed. We should record what the best course of action is and then apply it to the EOL versions we choose to retire/symlink.This would also simplify
build_docs.pya little bit.A