Extension directory should not promote alpha/beta relases if the develStage = stable
Currently CiviCRM recommends that admins always use the latest version of an extension, regardless if it is an alpha or beta release. This happens in-app and on the extension directory.
Proposal:
If the extension "Development Status" is set to "stable" on the ext directory, then ignore alpha/beta releases.
Implementation details: the easiest solution would be that the release-scanner would ignore alpha/beta in those situations.
- On the Extension directory: the big blue "Download" button should link to the latest stable
- In the list of releases: ignore alpha/beta, because they are noise
- Under the list of releases: we could link to the list of releases on Gitlab/Github and say "View all releases on Gitlab"?
Some people may have concerns about the visibility of beta releases, but I have to ask: what are their purpose? If they are for developers, then developers can get notifications via Gitlab/Github, or they might read an issue that says "go test this beta" with a link to gitlab/github.
Similarly, https://civicrm.org/download links to stable releases, and not beta. They are linked at the bottom.
If there are concerns about the level of support that admins/users should expect, I think that is a separate discussion (the short version has always been, as with core, "no expectations").