Features check with new version release

60 views
Skip to first unread message

arun ragha

unread,
Mar 9, 2022, 10:54:09 AM3/9/22
to blink-dev
Hi Team,

Our teams monitors chrome version releases to find any issues earlier.

Can you let us know if we can monitor the canary releases or is it required to monitor till beta release as we see new features are added or removed till dev and beta stage ?

Thanks
Arun

Eric Lawrence

unread,
Mar 9, 2022, 4:17:51 PM3/9/22
to blink-dev, arun ragha
How do you "monitor"?

I'm not aware of any cases where a feature made it into a Dev/Beta release without being in Canary first. (That said, it's possible to cherry-pick features from Canary into Dev/Beta releases after they were forked out of Canary). Things are slightly complicated by the fact that not all features are enabled in all branches. See https://textslashplain.com/2017/10/18/chrome-field-trials/ and https://textslashplain.com/2019/07/16/updating-browsers-quickly-flags-respins-and-components/ .

https://chromestatus.com/features/schedule is a good place to monitor changes.

arun ragha

unread,
Mar 10, 2022, 12:41:37 PM3/10/22
to blink-dev, eri...@microsoft.com
Hi,

Thanks for your answer. We use https://chromestatus.com/omaha_data to find the canary version and then use https://chromestatus.com/features_v2.json to pick the features related to that particular version. We have a jenkins job which runs this every week.

To pick up a specific case, for Chrome 100, till it was in canary and dev we saw only 7 features as part of the release but then in beta we now see 11 features as part of the release. Below 4 features were not part of the canary / dev release. Is this expected?


Regards,
Arun

Eric Lawrence

unread,
Mar 10, 2022, 12:41:44 PM3/10/22
to arun ragha, blink-dev

For some reason, I don’t see your reply in the discussion group.

 

Below, it sounds like you’re conflating “features as a part of the release” (what’s checked into the code) vs. “features that are listed on ChromeStatus as being part of the release” (documentation). Unfortunately, these aren’t the same things, and it’s certainly the case that features can go into Canary/Dev without an up-to-date ChromeStatus entry.

 

I believe Chrome’s tech writers push engineers to ensure that ChromeStatus is up-to-date at some point during the development cycle, but I believe this might happen around when Beta is forked.

 

-Eric

arun ragha

unread,
Mar 11, 2022, 4:53:56 PM3/11/22
to blink-dev, Eric Lawrence
Hi Eric,

I think then it is  better to track the chrome features till Beta is released to be sure of the exact features. Is that right?

FYI copying my previous reply below:

We use https://chromestatus.com/omaha_data to find the canary version and then use https://chromestatus.com/features_v2.json to pick the features related to that particular version. We have a jenkins job which runs this every week.

To pick up a specific case, for Chrome 100, till it was in canary and dev we saw only 7 features as part of the release but then in beta we now see 11 features as part of the release. Below 4 features were not part of the canary / dev release. Is this expected?


Regards,
Arun
Reply all
Reply to author
Forward
0 new messages