Versioning for repos that are not tagged with named release branches?

Some background: https://github.com/openedx/axim-engineering/issues/924#issuecomment-1765127544

Many Open-edX-related Python repos don't get tagged in named releases. That's because they are pip-installed into repos which are tagged. If we also tagged the pip-installed repos, then their tags wouldn't necessarily line up with the version(s) that tagged repos pip-install. (The same logic applies to JS libraries).

This process (tagging only top-level repos) has been the case since at least Juniper, and probably well before that too. @nedbat might know when we stopped tagging packages, and whether or not it was for the reason described above.

Does that clash with the fact that we use named releases in RTD version picker in https://docs.openedx.org/en/latest/ and elsewhere? What should we do for these pip-installed repos?

This is an open point of confusion in the release process: https://openedx.atlassian.net/wiki/spaces/COMM/pages/19662426/Process+to+Create+an+Open+edX+Release#5b.-Ask-Axim-to-activate-hidden-release-versions-of-each-book

Start by reading the background discussion in axim-engineering issue 924 and the RTD version picker references in docs.openedx.org. Review the linked Open edX release-process section on activating hidden release versions. Done means an agreed policy for versioning pip-installed Python and JavaScript repositories, with the relevant documentation updated.