As @Zizi64 explained, this is an utterly incorrect statement.
We have a proper pre-alpha, alpha, beta, and release candidate stages before officially releasing an X.Y.0, which is finally definitely not a beta at all. However, unlike many commercial products, we do not rush to force it to users, like when some new version of another office suite comes out, and all older versions disappear instantly from the offering. We realize that all the testing that the developers, QA, and enthusiastic users applied to the pre-releases is not a guarantee (everyone knows that even commercial software, spending millions on its QA, gives headaches to its early adopters soon after release every now and then); and we keep an older branch in parallel, as a recommended version. At the same time, without many users downloading and using the newly released X.Y.0, .1, etc., this newly released version would never improve anymore, and it would still create problems later. That is why we are very thankful to all the early adopters who use the fresh version - and we insist that it is not a beta at this stage.
Behaving responsibly and honestly may play bad joke to you. With everything else unchanged, discontinue version 7.3 the day you publish 7.4, and people will not be surprised. Provide choice keeping 7.3 in parallel, explain the difference - and people would have an opportunity to accuse you of abusing them as beta-testers.
I can only echo what @Zizi64 said:
Not beta-testers. We do everything we can to create good releases. But user testing is absolutely essential in the process, and we urge you to choose your branch wisely according to your needs.
Note that X.Y.4 is already not .0, .1, .2 - it is ready to become the next âstillâ, because itâs time when we discontinue 7.3, and release 7.5.0 (this February), the new fresh, at which stage, current 7.4 release becomes still.