James Butler

Hopefully it is not confusing to others to have `main` and `maint-X.Y` branches. I just realized the shortened term for “maintenance” is awfully close to “main” which is a totally...

https://github.com/Slicer/Slicer/commit/fff8c39ec7fcdeadbea8abf60b4220ab5821b8f0 (the v5.0.1 tag) which bumped to 5.0.1 doesn't currently belong to a branch. Is this to be added to the `maintenance/5.0` branch?

@jcfr Where would I go to update Slicer 5.0.x documentation separate from Slicer latest documentation? There’s currently documentation versions of https://slicer.readthedocs.io/en/v4.11/ https://slicer.readthedocs.io/en/latest/

Ah I see it is offsite managed in terms of the configuration. I've created a readthedocs account that is the same as my github (jamesobutler)

Yeah that's what I was thinking about in terms of how it would be displayed. If it matches the branch name then would likely need to change away from `maintenance/5.0`.

I think it should be enough to support updating documentation for the latest and stable release. Then older releases are just "locked in" to the documentation at time of tag.

> After someone makes the change there it is highly unlikely that the person will also spend the time with backporting/redoing the change to the stable branch as well. This...

Just thinking from a user perspective rather than a developer, it is quite frustrating to be using a stable release and the stable release documentation be out-of-date or lacking information....

Patching bugs (major and minor) in the stable release with continuous documentation updates would seem to be a good plan for the lifetime of the stable release until the next...

Just a selection of some applications where there is a typical given order for the Edit menu and that is with Undo/Redo and Cut/Copy/Paste at the top with other options...