How many Vivaldi beta releases before final?



  • I noticed the beta isn't numbered "beta 1" like the tech previews. So will there be anymore beta releases following this? Or is this the only beta before final?


  • Moderator

    @TsunamiZ:

    I noticed the beta isn't numbered "beta 1" like the tech previews. So will there be anymore beta releases following this? Or is this the only beta before final?

    If it's like other Chromium-based developments, it will just be "Beta" (possibly with a new version number for each step of Beta progress) until it is "Stable." I think we can expect Beta 1.0.303.52 through "Beta 1.0.whatever" until it is "Stable Version 1," the actual build number of which might be 1.0.522.12 or 1.1.1.3 or whatever.

    Soon we should also begin to see Developer Snapshots based on the Chromium 46 engine, and I expect these to be numbered 2.0.15.4 or something similar, and these will eventually become sufficiently mature to be Beta 2.0.221.6, and on ultimately to Stable Version 2."

    That's what I expect and, given the development pattern forced on people who use Chromium/Blink as their engine, there is almost no other sensible numbering scheme.



  • would be nice to get an official response on this, along with an ETA on the final


  • Moderator

    The official ETA for any stage of development with these developers has been for the last 20 years, and will always be, "When It's Ready."

    An official reply as to numbering might also be interesting. I'd enjoy reading one. But numbers aside, the PATTERN of development is forced by the nature of Chromium/Blink development to look like what I described. That is not something that can change.



  • @Ayespy:

    @TsunamiZ:

    Soon we should also begin to see Developer Snapshots based on the Chromium 46 engine, and I expect these to be numbered 2.0.15.4 or something similar, and these will eventually become sufficiently mature to be Beta 2.0.221.6, and on ultimately to Stable Version 2."

    Really? When do you think they will come out with Chromium 46? Hopefully before the end of the year? Hopefully before they come out with 47!

    What are all the improvements made in 46 compared to 45? I'm assuming mostly memory optimizations and cleanup of code, but I'm sure there are other fixes, additional features, etc.


  • Moderator

    @D0J0P:

    Really? When do you think they will come out with Chromium 46? Hopefully before the end of the year? Hopefully before they come out with 47!

    What are all the improvements made in 46 compared to 45? I'm assuming mostly memory optimizations and cleanup of code, but I'm sure there are other fixes, additional features, etc.

    Chromium 46 and 47 (and I'm pretty sure 48) are already out. Who knows what improvements there are in 46? Unless you are a Chrome developer, that's almost impossible to follow. By issuing its first stable version on Chromium 45, Vivaldi is actually a tiny bit behind the 8 ball. They need to begin a new version on top of 46 as soon as they have the resources freed up to do so. Opera Stable, on Chromium 46.0.2490.80, is already out, after having been in Beta for a couple of months. Of course they have over 100 desktop developers.

    Of course, Chromium 46 breaks several things that worked fine in browsers based on Chromium 45, which is why any browser built on each new version of Chromium engine has to go thru developer and beta stages for cleanup before it can reach stable. You NEVER put a new engine under a Beta or a Stable, because it will break a bunch of shit and set you back weeks in your development cycle. But every time a browser company adopts a new Chromium engine, this is the perfect time to add features and make modifications. Once it reaches Beta, you have to leave it alone and only bugfix and optimize it.



  • Yeah, I noticed that. Vivaldi is behind in the engine version. V 1.0 Stable will only have Chromium 45, and that's it. It's stuck in the way it is until 2.0 Stable comes along. But 2.0 is obviously going to come with Chromium 46, which is a bit disappointing if 47 is just around the corner or is already out.

    Doesn't Google have new stable release cycles every, what, 3-6 months? That means new Chromium versions tend to show up pretty quickly, and I'd like V to eventually get monetized so they too can grow big enough to catch up and use Chromium 47.

    Hopefully they change their minds and go with 47 in the new Alpha 2.0. I hope it's not too late. From what I understand, Chromium 47 is already in Beta as Chrome 47 Beta, so it would be ideal if Vivaldi followed it in the development of things.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.