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? 1. https://chromestatus.com/feature/5708770829139968 2. https://chromestatus.com/feature/5690646332440576 3. https://chromestatus.com/feature/5339955595313152 4. https://chromestatus.com/feature/5677338286096384 Regards, Arun On Thursday, 10 March 2022 at 23:11:44 UTC+5:30 Eric Lawrence wrote: > 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 > > > > *From:* arun ragha <[email protected]> > *Sent:* Thursday, March 10, 2022 3:48 AM > *To:* blink-dev <[email protected]> > *Cc:* Eric Lawrence <[email protected]> > *Subject:* Re: Features check with new version release > > > > 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? > > > > 1. https://chromestatus.com/feature/5708770829139968 > > 2. https://chromestatus.com/feature/5690646332440576 > > 3. https://chromestatus.com/feature/5339955595313152 > > 4. https://chromestatus.com/feature/5677338286096384 > > > > Regards, > > Arun > > > > On Thursday, 10 March 2022 at 02:47:51 UTC+5:30 [email protected] > wrote: > > 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/ > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftextslashplain.com%2F2017%2F10%2F18%2Fchrome-field-trials%2F&data=04%7C01%7CEric.Lawrence%40microsoft.com%7C9925be8e5a9946e8bd6308da027b06f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637825025589520787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=jnO9zoSIOZOHcM52dz0alkGAryzfrXZbY56e8X1SncM%3D&reserved=0> > > and > https://textslashplain.com/2019/07/16/updating-browsers-quickly-flags-respins-and-components/ > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftextslashplain.com%2F2019%2F07%2F16%2Fupdating-browsers-quickly-flags-respins-and-components%2F&data=04%7C01%7CEric.Lawrence%40microsoft.com%7C9925be8e5a9946e8bd6308da027b06f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637825025589570785%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=snGqOTiXnhN4bmA2ay%2FJMWaN9xwvR4snvKEgNn3W9Q4%3D&reserved=0> > > . > > > > https://chromestatus.com/features/schedule > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Ffeatures%2Fschedule&data=04%7C01%7CEric.Lawrence%40microsoft.com%7C9925be8e5a9946e8bd6308da027b06f0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637825025589570785%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CQCJ1TN1oJVcY3wFHicVEDOp3XFpCgQJRp9jzzKEMfg%3D&reserved=0> > > is a good place to monitor changes. > > On Wednesday, March 9, 2022 at 9:54:09 AM UTC-6 arun ragha wrote: > > 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 > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2683d4fe-762c-4a4f-b8c7-f6c54135ed5an%40chromium.org.
