@Mike , the thing that worries me about this, is that we have no clear idea as to where the line is for when YYG defines something as serious enough to warrant a forced update - and what you might consider important enough might not be the case for your users.
Furthermore, I've been using GMS almost daily since it was called GMHTML5 beta, and have never needed a forced update - if something was seriously messed up, I did a manual rollback. It might mean I'd miss out on a feature that was only included in an update that also happened to mess things up, but usually I could work my way around that and make the weighted decision
myself. I fail to see why GMS2 would be so different as to warrant this behaviour - in roughly 6
years of heavy and even commercial use of 1.x has this ever been necessary. Why now?
It's the same as we discussed on Skype with regards to data mining (in lack of better words) - less control is
always worse, no matter your intentions. Try to see this from a user perspective (and in this case, a user who always happens to take absolute worst case scenario into consideration)
EDIT:
For the record, I completely understand your reasonings for this throughout the beta, no worries there.
Once you go 1.x, though, that's another matter entirely.