Just as an interested observer.. The method used, is not a problem for tech types who are used to bugs and fixes. For 'normal' folks, bugs and problems and having to redo downloads, multiple times to 'fix' irritating problems SUCKS. And generally leaves a very very bad taste for the product involved.
So the method of letting customers find your 'bugs' for you may work in the short term. But long term, it means the brand (at least for software driven products) WILL get a bad reputation as buggy and crap.
My suggestion is you need to do a LOT more testing, with the goal of ZERO bugs and need for repeat updates. BEFORE your release software updates.
This from a non tech who has had my fill of bad updates in any form. I NEVER do any update. Just from experience they usually are worse than the problem being fixed. mainly, as I wrote, due to expecting ordinary folks to find your bugs for you.