When Mongo releases a new version, the downloads, release notes, and version selection in the support portal are never in sync and sometimes out of sync for weeks.

An example right now is 7.0.20. It has been out for a while. If I update via my OS's package manager, I get 7.0.20. Is 7.0.20 in the release archive download page? No. Does it have any published release notes? No. Is it selectable in the Versions list at support.mongodb.com? No. In fact, 7.0.19 is still not selectable there.

This is very frustrating and causes a lot of workflow/process issues. For example, Queryable Backups is broken on Amazon Linux 2023, so part of our documented process is "find the latest version and manually put it on the backup daemon box before running a queryable backup". Ops Manager will try to download 7.0.20 and fail, even though that's the latest version. How do we know it's going to download 7.0.20? We don't. If we check the Releases page, we think we need to download 7.0.19. The solution is to start a backup, watch it fail, see the version it tried to download, and correct it manually.

Please coordinate your release process better. Thank you.