Removing legacy modules and rarely used features from Slicer5

As you guys working towards Slicer 5, can I make the suggestion to start calling the 4.11 stream as as 5.0 preview?

There are few reasons for this. Primary reason is people new slicer do not initially appreciate how different current stable and the preview versions are under the hood. UI wise they look identical, but some of the changes, such as model coordinate system difference, python version, fiducial infrastructure etc, I think are more than you would anticipate in a minor version update.

I am not following the discussion closely, but Slicer 5 appears to have nebulous and rolling release timeline. As far as I can see most of the big changes is already there, the rest seems more like testing and removing functionality. So I see no harm calling the current preview as 5.0 preview.