Who's using Opera Beta is still affected by issues solved in Opera Stable: they should make 'v.70' available also in the beta channel (I don't care if they call it. And that's simply weird: a beta is supposed to 'be promoted' to Stable once that it's stable enough. I'm not complaining about the version number, the problem is that latest beta is not updated as latest stable. Salvuccino last edited by problem is that they don't share the same code. 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 : 70_Setup_圆4.Salvuccino last edited a software engineer, I always prefer to have a beta version ahead of stable in terms of fixes/updates/features. I don't get it: how much effort is actually needed to release Opera_ beta_. 60 release, so we're missing a bulk of fixes:ĭNA-75464 Crash at base::Time::Explode(bool, base::Time::Exploded*)ĭNA-76582 New tab button hover state should look like inactive hovered tabĭNA-76909 Crash at views::BridgedNativeWidgetImpl::SetParent(NSView*)ĭNA-76938 Rate Opera – black text on gray backgroundĭNA-76963 Crashes with easy setup panelĭNA-77341 Extensions actions should be hidden in overflow menu when they occupy more than 1/3 of toolbar size.ĭNA-77346 Use bigger tiles after update to R3 for some usersĭNA-77347 Tab preview stuck when dragging tabĭNA-77350 The location services disable button brings up an empty popupĭNA-77361 Crash at opera::PageView::is_locked()ĭNA-77390 Previous wallpaper color blinks when focusing tab with start pageĭNA-77403 Tailor font size for fallback tilesĭNA-77545 Opera crashes when trying to create snap Instead, Opera Beta is stuck at the 'old'.

Salvuccino last edited a software engineer, I always prefer to have a beta version ahead of stable in terms of fixes/updates/features.

Opera beta vs opera