.@jaffathecake / @addyosmani / @googlechrome question does chrome have specific criteria for a build to be promoted from 1 release channel to another?
What goes into a beta becoming stable?
-
-
-
Replying to @domenic @stefanpenner and
It also isn't a build, per sae. We branch from Dev -> Beta every ~6 weeks and then the Beta branch stabilizes/lands. We pick "good" builds from Beta when the crash rates/perf/etc. are all in good shape.
2 replies 0 retweets 3 likes -
Replying to @slightlylate @domenic and
So after 6 weeks, you basically use metrics to pick the best build within some window on beta, and promote it too stable? Thats pretty interesting, do you have any other details to share? Specifically, I'm curious how often these metrics break ties between builds and how often..
1 reply 0 retweets 1 like -
Replying to @stefanpenner @slightlylate and
an obvious "good build" surfaces?
1 reply 0 retweets 0 likes -
Replying to @stefanpenner @slightlylate and
Is it also the case, that per target platform different builds could surface as the "best build"?
1 reply 0 retweets 1 like -
Replying to @stefanpenner @domenic and
Yep! But the branch moves forward continuously. The usual wrinkle is that release on one platform may be slightly delayed or that fractional release may be paused if crash rates spike (e.g.)
1 reply 0 retweets 1 like -
n/p. Client software is hard, particularly at this scale, and these processes are hard-won knowledge. LMK if you have other questions!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.