christophe I have been having thoughts along the same line, but you beat me to it.
For me its super important to be able to move this beta into stable as soon as it is safe (I use mailbird a lot).
I have been solely using the beta in browser now for almost 2 weeks, and I am working the nerve of upgrading my desktop app to beta (perhaps this weekend will be the day).
I too have noticed that @Jay must be either busy with some of the bugs that we have been reporting, or distracted on something else, however I think we need to help by establishing what the correct criteria should be for greenlighting the deployment of this beta to the stable community. This forum is great for communicating but not good at helping prioritize the many things that come up, and it is up to Jay to comb through the whole thing and try to figure out which are the items that have the most impact to the community.
I propose each of the ones that have been testing the beta and reported bugs could self prioritize your own bugs and publish in a single post a list (only one liner description and a link to your original report) of your bugs grouped by priority… stating:
A - Critical bugs (things that unless fixed should prevent the beta from being released to the stable platform, because they prevent core operation of the software and have no workarounds, so therefore would disrupt peoples lives if released)
B- High Priority bugs (things that have high impact in the usage of the application, but have a workaround that could allow the use of the software if they were to be released, but nevertheless using the workaround is disruptive or a huge time waster)
C- Medium Priority bugs (things that impact the usage, annoy us, but have a simple workaround that doesnt make us waste too much time and we can honestly be patient enough to wait for a few releases to get them fixed)
D- Low Priority bugs (Mostly display formatting bugs that have no impact in functionality, although annoying or bothersome are things we all can live with).
And lets stick to bugs… no feature requests in those lists.
This could help @Jay focus on the A class bugs, get them fixed and have the agreed support of the beta community to release to stable community, with the agreement that class B bugs would be the next thing he would work on after the release to stable.
Thoughts? Ill be working through my list and try to post it as soon as I have it this weekend