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.j
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
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 Ch
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
