Final releases aren’t “final” releases which makes the betas not “betas”.
The terms don’t work with DVD Fab. The terms used to describe the software are square holes and the software is a round peg. They don’t fit together.
The terms used need to be changed to something that reflects the actual software. IF its a true beta like the first release of a new numbered version, ok, that’s a beta. When what is being released is an update to decryption algorithms, that’s an update, not a beta.
I’ve been around for some time. Nothing about a final release is final. And that is not a bad thing. The problem is not the software but the terms being used to tell us what to expect.
For a “beta”, I expect beta issues, try at your own risk, be ready to report bugs.
For a “final” release, I expect it to be a final release. Stable, mostly finished, may need an update once and awhile but what you see is what you get. You get used to how it works, you tackle the learning curve, you learn the ins and outs of the software as it is because what it is, it is going to be.
For an “update” I expect rarely to periodically see some fixes/tweaks to a few things, address security issues, maybe some cosmetics, a copy protection scheme, etc., but in general the core is left unchanged.
Those terms, except when a brand new next higher number version is in development, do not reflect how DVD Fab presents itself to the world.
The terms and the software need to dance the same dance.
As it is betas are not betas and final releases are not final releases. The current terms are outdated for how DVD Fab’s software is developed.