scikit-image stable release notes point to file on main branch

[jni]

Description

If you go to scikit-image.org and click on release notes, it points to the latest release notes — on the master branch. It should instead point to the release notes on the tagged release.

[alexdesiqueira]

@jni right now, it links to https://github.com/scikit-image/scikit-image/blob/main/doc/release/release_0.18.rst for me. What would we expect there?

[alexdesiqueira]

Maybe point to https://github.com/scikit-image/scikit-image/releases/latest?

[mkcor]

@jni right now, it links to https://github.com/scikit-image/scikit-image/blob/main/doc/release/release_0.18.rst for me.

@alexdesiqueira same here, and it doesn't seem odd to me. But I agree that

Maybe point to https://github.com/scikit-image/scikit-image/releases/latest?

looks nicer.

In the website repo, we should update master to main, in order to avoid the "Branch master was renamed to main" banner.

I don't get it because...
https://github.com/scikit-image/scikit-image-web/blob/0e2767e71509f1126d265da80f12fb14c25ba63b/_templates/sidebar_versions.html#L37
URL "https://github.com/scikit-image/scikit-image/tree/master/doc/release" doesn't include an actual file (release_0.18.rst).

[mkcor]

There's another link to 'release notes here' leading to https://scikit-image.org/docs/stable/release_notes.html

and it's consistent in the case of older versions (https://scikit-image.org/docs/<older version in 0.minor.x format>/release_notes_and_installation.html) but it's a little less intuitive for the dev version (https://scikit-image.org/docs/dev/release_notes.html):

[mkcor]

Now, my attention is drawn to the '(changes)' link next to 'API Reference' (see screenshots in the above comment)... It looks like the sequence is capped at Version 0.16:

• https://scikit-image.org/docs/dev/api_changes.html
• https://scikit-image.org/docs/stable/api_changes.html
• https://scikit-image.org/docs/0.18.x/api_changes.html
• https://scikit-image.org/docs/0.17.x/api_changes.html
• https://scikit-image.org/docs/0.16.x/api_changes.html
• https://scikit-image.org/docs/0.15.x/api_changes.html
• ...

[jni]

I don't have strong ideas here. My main motivation for this was that releases happened on branches, so the main branch notes could be out of date with the release branch. Now that we are making releases just with tags + CI (no branching), that is less of a concern. Although #5475 might change that temporarily yet again. 😅 I think though that ideally, yes, we should render release notes in the docs and use that, as napari does.