-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAINT: Archive old doc versions #11885
Comments
crossref: #10932 I can't think of a good reason to keep the very old website versions available online. It would be nice if they existed somewhere --- could we have a separate branch of the
2 years would go back to 0.23, 3 years would include back to 0.21. My feeling is that things are starting to stabilize and the package is maturing, which means people may become less likely to habitually update all the time, which means installs of a particular version might hang around for longer, so it might be good to preserve 3 years worth of docs instead of 2. |
I was thinking we'd just create archives like |
adding an For now let's ZIP and we can worry about adding access to the ZIPs at a (not too much) later date... unless you already have a clear idea where this page should live, in which case go for it. |
We currently have a version drop-down all the way to 0.11, which I think is rarely used or completely unused. Also when pushing commits to
mne-tools.github.io
repo I get warnings like this that suggest that our HTML has vulnerabilities, which is presumably due to ancient webpages:I suggest we put some lower bound on which versions to archive -- maybe the last 2 years worth of versions? This should help reduce this security issue, and also make the site faster to deploy and fetch, etc. If we don't want to get rid of the 0.11 docs entirely for example we could archive them in a
.zip
and link to them somewhere in our docs. This could easily be added as another step in our release process, and I don't think it would take too much extra time/effort (< 10 min) during release time.Any objections? @drammock I'm releasing today but can take care of the changes this week and backport them to the
maint/1.5
branch I'm going to make (so that links to the archived versions exist).The text was updated successfully, but these errors were encountered: