I do understand your eagerness, but I prefer a release that is a few days later or more, over an early beta that still contains bugs. Because that would mean another beta.
I really prefer the developers take more time and therefore less stress and errors, to bring out a better beta.
A more different, more step-by-step schedule would be a beta 1 at date 1, a beta 2 at date 2, a beta 3 at date 3. And maybe then the beta3 is not even necessary. And then a release candidate RC1, RC2, etcetera on planned dates.
Or you chose to release a beta when you are ready for it.
Two different release strategies I have seen, and been working with in the past 30 years.