-
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: Clean up whats_new and doc versions #11888
Conversation
* upstream/main: MAINT: Post-release deprecations, updates [circle deploy] (mne-tools#11887)
This almost works: But it links to |
Note that I didn't update |
doc/whats_new.rst
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick]: making this into a "landing page" makes the page content 100% redundant with what's in the sidebar TOC. For mobile / small screens that's OK (arguably good?) but for big screens it looks odd to me. No action necessary unless it also bothers you and you have an idea how to fix it.
[more serious concern]: how will this page look on stable
vs dev
? I'm guessing that at release time the entry for changes/devel.rst
gets altered to changes/v1.6.rst
or similar, and then a new entry gets inserted for devel
after the release is cut. Is that right? If so, has the releases Wiki been updated accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For mobile / small screens that's OK (arguably good?) but for big screens it looks odd to me. No action necessary unless it also bothers you and you have an idea how to fix it.
Yes I don't like it either but I think we can improve it later. Ideally pydata-sphinx-theme would allow per-page config of which sidebars to show / how to configure them. I guess we could probably do it already with themes since we do it with the homepage / index.html
... but I think we can do it as a follow-up PR.
[more serious concern]: how will this page look on stable vs dev? I'm guessing that at release time the entry for changes/devel.rst gets altered to changes/v1.6.rst or similar, and then a new entry gets inserted for devel after the release is cut. Is that right?
Yes. So stable/
will not have the dev changes -- the topmost link will be to the X.Y
release, which seems correct to me.
If so, has the releases Wiki been updated accordingly?
No I'll do that stuff after we merge, I'll add it to the TODO list at the top.
ouch that is not pretty. There are some changes to version switcher JSON in the dev version of the theme, so there's a chance it's already fixed but I'd have to check. For now please do switch so that it lives mne.tools/dev/old_versions/index.html Relatedly, do we need to specify a numeric version for "older..."? I think it might work to just say the version is "old" (but again, maybe only with dev version of theme). FYI I'm trying to get a new version of the theme released soon so feel free to just get it working and don't worry about testing against dev version of theme; I'll be doing that soon enough anyway. |
Co-authored-by: Daniel McCloy <dan@mccloy.info>
Done!
I actually kind of like the idea of changing it to |
* upstream/main: Refactor test_epochs.py::test_split_saving (2 out of 2) (mne-tools#11884) Cross-figure event passing system (mne-tools#11685)
Comments addressed and I wanted to get the |
And I'm a bit confused by the fact that version 1.3.1 is shown in the new changelog (notice the patch version increment): Whereas all other options are without patch increments (even if such versions were released, see: https://github.com/mne-tools/mne-python/releases). Other than that, and the comment about the error 404 above, I am happy with the changes here. thanks a lot @larsoner! |
The version dropdown it works for me (on https://mne.tools/0.21/index.html As does the https://mne.tools/dev/changes/v0.20.html But it does look like there are corner cases:
The first one we can fix with trivial redirect The second one is hopefully low impact since I think if people want docs like 0.22 they'll go there first from the landing |
Okay, works for me as well now -- thanks for the explanations. However what about this odd-one-out item?
In my opinion either:
|
Indeed that should not be in the changelog I think. The point releases pretty much always contain redundant changes with the next major release... |
... snuck 1.3.1 cleanup into #11890 since that's marked for merge-when-green |
* upstream/main: [pre-commit.ci] pre-commit autoupdate (mne-tools#11911) [BUG, MRG] Remove check on `mne.viz.Brain.add_volume_labels` (mne-tools#11889) Small splits fix (mne-tools#11905) adds niseq package to "Related software" (mne-tools#11909) Minor fixes for ERDS maps example (mne-tools#11904) FIX: Fix pyvista rendering (mne-tools#11896) BUG: Fix epoch splits naming (mne-tools#11876) ENH: Use section-title for HTML anchors in Report (mne-tools#11890) CI: Deploy [circle deploy] MAINT: Clean up whats_new and doc versions (mne-tools#11888) Refactor test_epochs.py::test_split_saving (2 out of 2) (mne-tools#11884) Cross-figure event passing system (mne-tools#11685) MAINT: Post-release deprecations, updates [circle deploy] (mne-tools#11887) MAINT: Release 1.5.0 (mne-tools#11886) [pre-commit.ci] pre-commit autoupdate (mne-tools#11883) Refactor test_epochs.py::test_split_saving (1 out of 2) (mne-tools#11880) FIX: Missing Saccade information in Eyelink File (mne-tools#11877) Improve drawing of annotations with matplotlib (mne-tools#11855) MAINT: Work around NumPy deprecation (mne-tools#11878)
Co-authored-by: Daniel McCloy <dan@mccloy.info>
whats_new
to show latest changes and link to all othersrst_prolog
so we don't need to.. include:: links.inc
and.. currentmodule:: mne
all over the placelinks.inc
to be much shorter and remove a lot of stuff we don't use (didn't check everything but checked some stuff at least)@drammock let me know what you think. @sappelhoff also feel free to look since you had a preference for the long, continuous
whats_new.html
in #10789 . Will post CircleCI links once they render.WIP until approved, then I'll:
versions.json
from this branch0.11
through0.20
folders andversions_temp.json
frommne-tools.github.io