How can one know if a bug fix made its way to the public stable release?

[Stephane Leduc]

In the context of the upgrade of a web-extension to Manifest v3, I have quickly came across this Chromium issue.
Apparently, a fix has been published but it seems associated to the Chromium Canary channel. Now I new to know if the fix has already made its way to the Chrome stable release. I have spent some time looking in the releases log files but with no luck ...

How am I supposed to make sure the fix does have been brought to Chrome "desktop stable" channel? 

Thank you.

[PhistucK]

https://chromiumdash.appspot.com/ can help, you need the commit hash from the comments of the bug, if any.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/2e44c693-6c2c-4ac6-a152-b3d84ebf1b84n%40chromium.org.

[Stephane Leduc]

This dashboard is really convinient!

I now know that the fix apparently landed on Chromium Stable — v107.0.5304.54.
I was wondering how Chrome release number relates to Chromium version numbers ...
Correct me if I am wrong but looking at the log file found at 25th of october Chrome release page, the fix seems to have been included.

Thank you!

[wOxxOm]

Chromium version number always ends on .0 i.e. 107.0.5304.0, it's always linear. The last number changes in Google Chrome releases that include back-merged fixes from the "future" of this version. Commits are pushed into the trunk branch linearly and each commit receives a revision number like 1043598 in the fix you're looking for. Binaries are built for each commit by internal Google build bots. Every few hours the latest binary for each platform is pushed into the snapshot repository, there's a download page for the latest binary, there's also the official bisect-builds.py script that downloads from this repository. Every day/week/month/quarter or so Chrome Canary/Dev/Beta/Stable is released, its revision being 0. When there are important fixes they are first committed as usual into the linear trunk branch, then tested in Canary for a day, then back-merged into the more stable channels, then the last number in the version string is increased and a new update is released. There's also another official resolver at https://omahaproxy.appspot.com - click "Find release" and paste a commit hash or revision number and it'll show versions that include the original commit and its back-merges into current Chrome channels.

[PhistucK]

Chrome versions and Chromium versions are based on the same code/commit. Chrome has a bit more code that Chromium lacks, but it is generally the same code.

However, Chromium does not have official releases/stable versions. Chromium is the project, not the browser/application.

Some third parties package their own Chromium derivatives, some of them are actually named "Chromium", but those are sometimes modified versions and are unrelated to the project.

☆PhistucK

[Stephane Leduc]

What a good big-picture with the relevant details. I really appreciate, thank you! 👍

[hrg...@gmail.com]

However, Chromium does not have official releases/stable versions.

Chromium DOES have official builds and developer builds. Official version numbers are the same in both Chrome and Chromium.

For example, Chromium 104.0.5112.102 is an official build and this corresponds to Chrome 104.0.5112.102 which is also an official build.

Chromium version number always ends on .0 i.e. 107.0.5304.0

I've never seen official releases ending on .0

We see this on developer builds, but not always. See this link for more info:

https://vikyd.github.io/download-chromium-history-version/#/

 

[wOxxOm]

The vikyd.github.io lists versions of custom Chromium builds, which is why there are revision numbers other than 0.

The original Chromium is an official build of Chromium from the original unaltered source. Such builds are produced automatically by Google's build bots and can be downloaded from the snapshots repository or https://download-chromium.appspot.com (the latest build). They always have 0 revision number because they are always built from current source linearly, no back-merges.

[wOxxOm]

To clarify, it doesn't have to be an official build by Google of course, but it's the only one I know of that uses the unaltered source code for 100%.

[wOxxOm]

BTW that vikyd.github.io page lists Chrome versions with non-0 revision, not Chromium versions, which are linked in the second column and serve as the base for Chrome version on top of which the back-merges and other stuff is added.

[hrg...@gmail.com]

What about the versions we see here?

https://chromium.googlesource.com/chromium/src/+refs

Are those not the unaltered source code?

[PhistucK]

No, Chromium does not have official builds. Any Google-provided builds available for download are for testing purposes, not for using it as a proper browser. The project does not recommend using them, nor does it advertise them as such, especially because they do not update automatically and because they are unstable, may contain severe security issues as they are completely untested (by humans) and other similar reasons.

☆PhistucK

[wOxxOm]

> https://chromium.googlesource.com/chromium/src/+refs

As there's no official Chromium build for these tags, apparently these are Chrome versions slapped into Chromium's source code for convenience of tracking the back-merged commits.

[wOxxOm]

On the other hand, I guess it can be said that this is a Chromium version if we consider Chrome releases an integral part of Chromium.