All the releases with large numbers of downloads must be relatively stable, otherwise I'd have a lot of people complaining.
Any release with very low numbers of downloads, or when there has been a second update on the same day, is likely to have problems.
I try to keep the Betas as stable as possible,but there have been multiple occasions where there have been problems.
Because there are only 2 levels of version available to me on the GitHub storage, (either "Pre-Release" which I label as a Beta, and "Release" which I label as release"), its difficult for me.
Normally projects have at least 3 levels of releases.
Stable , Latest / Beta , and "Nightly"
But I don't have the option to mark something as a Nightly
People have suggested I do automated builds and make these available, but this would be problematic, because just the other day, I did something which worked fine on my radio, and also on 2 other Beta testers radios, but another Beta tester had serious problems and his radio hung and would not turn off, and he had to remove the battery and then plug the battery back in whilst holding down the buttons to allow him to reload the older firmware
I can't risk putting those versions out by accident, because of automated "Nightly" builds.
In fact with the change that caused this problem, I'm going to need to post an experimental release for anyone willing to take the risk, as a completely separate download from a file on my Google drive
Edit..
e.g.
viewtopic.php?f=7&t=1487&p=13069#p13069