GeezerVison

coverage: 94.745%. remained the same
when pulling b3d8ce9 on murrayrm:release_notes-07Mar2025
into 2745b12 on python-control:main.

If you have access to the ReadTheDocs admin panel, it is worth checking why a warning banner is not appearing on older versions, #1131 (comment)

I looked into this and the settings are such that we should see warning banners. But we don't. I've added @slivingston as a maintainer in case you have time to look and want to debug.

If you have access to the ReadTheDocs admin panel, it is worth checking why a warning banner is not appearing on older versions, #1131 (comment)

I looked into this and the settings are such that we should see warning banners. But we don't. I've added @slivingston as a maintainer in case you have time to look and want to debug.

Thanks. It turns out that ReadTheDocs follows the Semantic Version specification, which states that versions less than 1.0.0 are for "initial development" and not stable. ReadTheDocs allows us to manually declare which version is stable by pushing a branch named stable, which I did. Now viewing older versions or "latest" (!= stable) shows warning banners as we want.

Thanks for the ReadTheDocs fix, @slivingston. What do we need to do when we make a new release? Copy that release into stable?

Thanks for the ReadTheDocs fix, @slivingston. What do we need to do when we make a new release? Copy that release into stable?

Yes. Basically, the branch should point to the same commit as the tag used for the release:

git checkout stable
git merge 0.10.2
git push