Since this thread has morphed to discussing extending the initial “Rolling Content Views” feature to environments other than Library, here is one more update on the approach we are now actually implementing:
After much back and forth, we are now going for “maximum flexibility and user choice”. In other words, it will be possible to expose rolling content views to arbitrary lifecycle environments (including multiple environments at a time). This is a full solution that is least likely to prompt immediate user requests for further extensions. We also found that once you have the building blocks for exposing rolling content to one environment other than library it is not that much more work to make it fully flexible.
In a nutshell: Maximum flexibility and no magic names.