Just to chime in: I take issues at the release strategy of these firmwares.
What are the betas for? test the build to iron out bugs after the addition of new features.
So each beta should be used to add features and released to us only after initial testing showed reasonable stability (alpha phase).
We, the customers who are willing, test and report bugs, and through different iterations you fix the bugs to the point where most of them are resolved and you can create a release build.
Then you restart the process on a new beta with new features etc etc...
I am seeing MCV doing completely the opposite. You have us a test a beta builds which then on the release comes with a ton of new features which create other bugs. Which then have fixes promised on the next betas. The result is that you have very unstable new releases. Firmware management has been a monstrous failure. I am tired of seeing new releases more unstable than the previous with new features of various level of usefulness added and apparently so are many other customers who have turned the veras into frisbees.
Having incompletely tested beta builds, I can understand, but releasing firmware with device killing bugs, which have been reported for months, not fixed and instead, adding a bunch of new device support or new features, such as ACM on this latest build, released between beta and release is what is killing you.
You should release betas also at a much higher rate with bug fixes only. You obviously have bugs being fixed but we have no idea why you want to have customer support manually implementing them to customers who complain as we hear about on this forum. The fixes should be in the beta build iterations where you experiment with new features.
Sorry for the grumbling but wanted to suggest improvements to your firmware development and release strategy.