In any case, I'll likely switch to stable, because if beta is not always ahead of stable (=being able to test/use recent fixes), it makes no sense to use it. Now you are welcome to laugh with everybody else, usual fanbois of this blog excluded of course. The situation is the following though lol, stable left out the oven so early (like always) and because it is so broken it acts like the beta, so stable and beta are updated at the same time to 3255.37, 3255.56, 3255.57, 3255.59, 3255.60, now to 3255.70 and will get probably at least 5 updates more. At this point both stable and beta should have the same build number, stable does not need any further updates by definition and the next stream with the new 'locked' developement features goes to the other stream (beta) to get its bugs fixed, in this case 61. In this case -as in almost every other case in the past- if you check the changelogs, 'theoretically' Opera beta was ready to be promoted at version 3255.27 in April, 9th.
'In a serious company that respects its own words/statements the beta reaches a point where there are no bugs left to fix so the last version of it is being promoted to stable.
There's an interesting thread about it on Opera blogs and I'm not alone : Salvuccino last edited a software engineer, I always prefer to have a beta version ahead of stable in terms of fixes/updates/features.