Beta release after Stable release
What do you suggest?
TER allows developers to release a beta release after a stable release.
I would suggest to trick users into the stable release where possible. Only if users want to try things out, they can also use the beta release.
As an extension developer, I want to get user feedback for the latest changes as long as I'm not sure if the latest version is suitable for most users.
If I release beta software as a stable version, it might brick a lot of production systems. If I don't release it at all, I don't get any feedback (unless users try it out via github or manually tweak their composer.json). Without feedback, I still don't know if the new release might brick something.
But if I release it as a beta version, everything on TER goes yellow, although a stable green version would be available as well. Users are tricked into using a beta version or not using the extension at all (because it seems to be beta).
Add an use case
We released the first 2.0.x releases of metaseo as beta versions, and got lots of feedback which helped us to fix a lot of bugs. https://extensions.typo3.org/extension/metaseo/
However, TER warned of beta software for a long time so that especially 6.2 users eventually did not use metaseo because it seemed to be beta (although stable versions were available for 6.2 as well).
Currently, I'd like to add a bunch of new features to metaseo (which still is compatible against 6.2 LTS, 7.6 LTS, 8.7 LTS) and eventually release a .0 as beta version to get some feedback.