This is a good idea, but it is not clear how it will be implemented. The main issue is selection of features for proposed ‘Public Betas’.
wouldn’t it make decisions far more easier if we have an easy way of finding what those features are and what is the interest from community/market for each one of them? We had a related discussion earlier regarding this as part of long term roadmap discussion(ERPNext Roadmap Document [Long Term Goal] - #13 by spoojary). If we have a list of prioritized road map items($ + Dev time), selecting what should go to ‘Public Beta’ becomes a non-issue. That way even a core feature like ‘upgrade stability’ might show up above all other features if there are enough people considering it as an issue and are ready to pay for making it better.