Jean-Christophe Fillion-Robin

Since we already have the tag called `vX.Y.Z`, using `X.Y-maint` is sensible and would avoid confusing both.

Branches have been renamed to `maint-5.0` and `maint-4.11` > calling the branch v5.1 Since the maintenance branch is for releasing patch release associated with the `5.0` series, I kept `5.0`...

Thanks everyone the feedback, this is very helpful. * [x] Create tag `v4.11.20220218` * See https://github.com/Slicer/Slicer/releases/tag/v4.11.20220218 * Command used was ``` X=4 Y=11 Z=20220218 echo "X.Y.Z is ${X}.${Y}.${Z}" GIT_TAG=v${X}.${Y}.${Z} echo...

> Is this to be added to the maintenance/5.0 branch? Indeed, I just pushed the last commit corresponding to `v5.0.1` and as of today, both `v5.0.1` and `maintenance/5.0` match.

Thanks for following up on this :pray: So that you can help, I could add you a maintainer on the corresponding readthedocs project. Do you happen to have a readthedocs...

> readthedocs @jamesobutler I just added you. We could have a mapping from `maintenance/5.0` GitHub branch to `v5.0` readthedocs version. That said, the name associated with a given version is...

For now, I suggest we have the following versions public: ``` https://slicer.readthedocs.io/en/latest/ https://slicer.readthedocs.io/en/stable/ https://slicer.readthedocs.io/en/v4.11/ https://slicer.readthedocs.io/en/v5.0.2/ ``` If we have the needs to update the 5.0 documentation without having to create...

> I would be willing to contributes changes to update the stable documentation so that the user could quickly review the new documentation. To accommodate this, a possible path forward...

> I liked the consistency with other software but the experiencing the extra difficulty on using the menu (it takes at least 2x longer time to click on the last...

Historical datasets have all been archived in this project. See https://github.com/Slicer/slicer.kitware.com-midas3-archive#readme Do we need to create a static page or is it sufficient to have the following: * support for...