Opera 120.0.5543.53 beta update
-
-
andrew84 last edited by andrew84
@leocg said in Opera 120.0.5543.53 beta update:
There's 120 stable and 120 beta at the moment
That's what was the initial question about.
-
whisperer last edited by@leocg said in Opera 120.0.5543.53 beta update:
@whisperer There's 120 stable and 120 beta at the moment.
You mean a beta that according to its changelog promotes itself to a stable version but still remains a beta?
-
leocg Moderator Volunteer last edited by
@whisperer Think about channels and not versions.
Stable channel version is 120 and Beta channel version is also 120.
Anyway, they do it because many people have been asking through the years.
-
daria19 Opera last edited by
@francehelders: Hello! Beta is at 120.0.5543.53 and Stable is at 120.0.5543.61. Even though the version number 120 is the same, they’re on separate update tracks. The changelog line about "promoting to stable" just means that particular build was pushed to the stable channel - it doesn’t mean the beta channel stops updating.
Thanks for your comment! -
-
whisperer last edited by
@daria19 said in Opera 120.0.5543.53 beta update:
@francehelders: Hello! Beta is at 120.0.5543.53 and Stable is at 120.0.5543.61. Even though the version number 120 is the same, they’re on separate update tracks. The changelog line about "promoting to stable" just means that particular build was pushed to the stable channel...
So, you are saying that the changelog entry "promoting to stable" in the changelog of build 120.0.5543.53 means that build was pushed to the stable channel. But it never was, right?
-
daria19 Opera last edited by daria19
@whisperer The changelog entry saying "promoting to stable" means that version 120 was promoted to the stable channel - but not necessarily that that exact build (e.g., 120.0.5543.53) is itself the stable build. As mentioned in the previous comment, it's important to remember that versions and channels are separate, which can understandably be a bit confusing.
To add some context: the previous changelog entry for version 120 was about its initial stable release, and the next one referencing 120 was for the beta channel. That beta changelog includes the note that 120 is now available not only in beta but also in stable, which signals the promotion.
-
leocg Moderator Volunteer last edited by
@andrew84 Yep, it used to be that way, when a version was promoted to stable channel, the beta one would only be updated when a version was promoted from Developer to Beta.
However, some people started complaining that Beta would be behind stable and Opera seems to have decided to update Beta channel even its version being the same as Stable.And I remember that they once said that you should follow channels and not versions.
-
andrew84 last edited by andrew84
@leocg said in Opera 120.0.5543.53 beta update:
Beta would be behind stable
This Beta (.53) is already behind the Stable (.61). So the correct would be to update Beta 120 to 121 (if it's ready to be promoted). If not ready, then wait when it'll be ready and promote to 121. So what does the one day interval decide here is not clear.
*If there's some automatic announcement system (includes AI) which monitors releases, then it would explain the confuse.
-
whisperer last edited by
@daria19 said in Opera 120.0.5543.53 beta update:
To add some context: the previous changelog entry for version 120 was about its initial stable release, and the next one referencing 120 was for the beta channel. That beta changelog includes the note that 120 is now available not only in beta but also in stable, which signals the promotion.
There is a beta changelog? Cool. Where is it? I have only seen the full changelog which contains changes of beta and stable versions without distinction.
If you need to repeat a change for an earlier stable version, why not for all the changes of the earlier stable version?
-
-
leocg Moderator Volunteer last edited by
@whisperer The changelog is for the whole version.
You can see what changes were made during beta stage by looking at the build numbers.
-
whisperer last edited by
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer The changelog is for the whole version.
You can see what changes were made during beta stage by looking at the build numbers.
Exactly my point.
-
leocg Moderator Volunteer last edited by
@whisperer And I think you are trying to complicate things unnecessarily.
-
whisperer last edited by
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer And I think you are trying to complicate things unnecessarily.
Enlighten me, what am I trying to complicate unnecessarily and how am I trying to do that?
-
leocg Moderator Volunteer last edited by
@whisperer Everything that is being discussed here about Beta channel have been updated to the same version of stable channel.
It's not something new, Opera has been doing it since a while already and, like I said, started by request of (some) users.
Also, Opera once said that people should follow channels and not version numbers, that only exist to make things easier for people.
-
whisperer last edited by
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer Everything that is being discussed here about Beta channel have been updated to the same version of stable channel.
It's not something new, Opera has been doing it since a while already and, like I said, started by request of (some) users.
Also, Opera once said that people should follow channels and not version numbers, that only exist to make things easier for people.
That's not an answer to my question. If you are not willing to explain why you think I am unnecessarily trying to complicate things, I respectfully ask you to refrain from posting off-topic thoughts about me and stick to discussions about Opera.
I have no trouble with the existence of beta and stable builds with the same major version number. But I do have trouble with the changelog entry "DNA-123014 Promote 120 to stable" listed for the build 120.0.5543.53 in the full changelog. From the user's perspective that doesn't make sense.
As you yourself said: "You can see what changes were made during beta stage by looking at the build numbers." That's not the case for this changelog entry. The explanation given that the full changelog consists of a combination of indistinguishable beta and a stable changelogs where the beta changelog can contain entries that doesn't apply to the build it is listed under, but to an earlier build, doesn't make it logical and understandable for users.
-
burnout426 Volunteer last edited by
@whisperer said in Opera 120.0.5543.53 beta update:
he full changelog consists of a combination of indistinguishable beta and a stable changelogs
Note that there are Opera Developer builds in each changelog too. The changelog contains changes for all released builds for that major version whether they're developer, beta or stable. Hovering over the "blog post" link for each and looking at the URL will show whether it's a developer, beta or stable build. You can even see if it's the initial developer/beta/stable build for that major version by the lack of "-update" in the URL. Think it would be nice if that info was in the header for each build though in the changelog.
You should also notice that change log for the initial stable build at least is huge because it's not just the changes from the last build before it like the "-update" builds. So, you're going to see duplicate entries (the promote thing for example doesn't bother me).
Sure, things could probably be improved in different ways, but it might be more work.
-
whisperer last edited by
@burnout426 said in Opera 120.0.5543.53 beta update:
Hovering over the "blog post" link for each and looking at the URL will show whether it's a developer, beta or stable build. You can even see if it's the initial developer/beta/stable build for that major version by the lack of "-update" in the URL. Think it would be nice if that info was in the header for each build though in the changelog.
That would indeed improve clarity. Additionally, a link to a page with an explanation of full changelog pages could be helpful too.
