When running "dist/s_docs -l" to generate documentation for a new OSS release, in the generated index.html file the "current" version is replaced with the new version (e.g. 11.0.0) to be released but the "previous" version is left unchanged (e.g. 3.2.1). It is expected the "previous current" version (e.g. 10.0.0) would be moved to the "previous" version instead (the cascading effect). 

We should make the expected behavior about current/previous version settings on the documentation front page automated and built into the release workflow.