Google halts Chrome, Chrome OS releases to avoid shipping flawed code, prioritizes security fixes amid coronavirus crunch
(2020/03/19)
- Reference: 1584583565
- News link: https://www.theregister.co.uk/2020/03/19/google_halts_chrome_releases/
- Source link:
Google has suspended Chrome browser updates after failing to release Chrome 81 on Tuesday.
Though the Chocolate Factory announced the availability of Chrome 81 on March 17, as scheduled on its [1]Chrome Release Status page, the updated code did not get distributed. The problem can be attributed to COVID-19, specifically what the pandemic has done to the availability of Google engineers.
"Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases," Google said on Wednesday in a [2]blog post .
"Our primary objectives are to ensure Chrome continues to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80."
Google: You know we said that Chrome tracker contained no personally identifiable info? Yeah, about that... [3]READ MORE
On Wednesday, Chrome team shipped just such a security-focused update, bumping Chrome build 80.0.3987.132 to 80.0.3987.149. The revision addresses [4]13 browser vulnerabilities , nine of them designated high severity.
The Register asked a Google spokesperson to elaborate on the specific technical issue that delayed Chrome 81 but we've yet to receive a response.
A glance at the [5]Chrome bug tracking system suggests that recently reported bugs, code regressions, or missing or failed build tests may have played a role in the snafu.
Via Twitter on Tuesday, Jordan Austin, a developer at edutech biz Vernier Software & Technology, [6]said he'd "filed a bug against Chrome 81 beta that would be a disaster for my company if it goes to stable." [7]The bug prevents video from appearing under certain conditions.
[8]Chrome 81 , released February 13 on the beta channel, includes several novel capabilities, including Web NFC, a browser implementation of Near Field Communications that allows developers to read and write NFC tags from mobile web apps, and VR/AR API enhancements for making browser-based virtual and augmented reality apps.
The update adds numerous developer-focused features, version 8.1 of Google's V8 JavaScript engine, and [9]modernized form controls . It also removes TLS 1.0 and TLS 1.1 support, given that those protocols have known shortcomings.
Chrome 81 is also supposed to [10]add Ecosia , a search engine that uses revenue to plant trees, as a default search engine option alongside Google Search, Bing, DuckDuckGo and Yahoo in 47 countries where such choice is offered. ®
[1] https://www.chromestatus.com/features/schedule
[2] https://blog.chromium.org/2020/03/upcoming-chrome-releases.html
[3] https://www.theregister.co.uk/2020/03/11/google_personally_identifiable_info/
[4] https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_18.html
[5] https://bugs.chromium.org/p/chromium/issues/list?q=M%3D81&can=2&sort=-modified
[6] https://twitter.com/jordaust/status/1240049223782957056?s=20
[7] https://bugs.chromium.org/p/chromium/issues/detail?id=1062002&sort=-modified&q=M%3D81%20jaustin&can=2
[8] https://blog.chromium.org/2020/02/chrome-81-near-field-communications.html
[9] http://concrete-hardboard.glitch.me/
[10] https://blog.ecosia.org/ecosia-default-search-engine-option-chrome-browser/
Though the Chocolate Factory announced the availability of Chrome 81 on March 17, as scheduled on its [1]Chrome Release Status page, the updated code did not get distributed. The problem can be attributed to COVID-19, specifically what the pandemic has done to the availability of Google engineers.
"Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases," Google said on Wednesday in a [2]blog post .
"Our primary objectives are to ensure Chrome continues to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80."
Google: You know we said that Chrome tracker contained no personally identifiable info? Yeah, about that... [3]READ MORE
On Wednesday, Chrome team shipped just such a security-focused update, bumping Chrome build 80.0.3987.132 to 80.0.3987.149. The revision addresses [4]13 browser vulnerabilities , nine of them designated high severity.
The Register asked a Google spokesperson to elaborate on the specific technical issue that delayed Chrome 81 but we've yet to receive a response.
A glance at the [5]Chrome bug tracking system suggests that recently reported bugs, code regressions, or missing or failed build tests may have played a role in the snafu.
Via Twitter on Tuesday, Jordan Austin, a developer at edutech biz Vernier Software & Technology, [6]said he'd "filed a bug against Chrome 81 beta that would be a disaster for my company if it goes to stable." [7]The bug prevents video from appearing under certain conditions.
[8]Chrome 81 , released February 13 on the beta channel, includes several novel capabilities, including Web NFC, a browser implementation of Near Field Communications that allows developers to read and write NFC tags from mobile web apps, and VR/AR API enhancements for making browser-based virtual and augmented reality apps.
The update adds numerous developer-focused features, version 8.1 of Google's V8 JavaScript engine, and [9]modernized form controls . It also removes TLS 1.0 and TLS 1.1 support, given that those protocols have known shortcomings.
Chrome 81 is also supposed to [10]add Ecosia , a search engine that uses revenue to plant trees, as a default search engine option alongside Google Search, Bing, DuckDuckGo and Yahoo in 47 countries where such choice is offered. ®
[1] https://www.chromestatus.com/features/schedule
[2] https://blog.chromium.org/2020/03/upcoming-chrome-releases.html
[3] https://www.theregister.co.uk/2020/03/11/google_personally_identifiable_info/
[4] https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_18.html
[5] https://bugs.chromium.org/p/chromium/issues/list?q=M%3D81&can=2&sort=-modified
[6] https://twitter.com/jordaust/status/1240049223782957056?s=20
[7] https://bugs.chromium.org/p/chromium/issues/detail?id=1062002&sort=-modified&q=M%3D81%20jaustin&can=2
[8] https://blog.chromium.org/2020/02/chrome-81-near-field-communications.html
[9] http://concrete-hardboard.glitch.me/
[10] https://blog.ecosia.org/ecosia-default-search-engine-option-chrome-browser/
Clock is running...
RyokuMas
So - due to "engineer availability", Google may not have the people required to fix issues in Chrome - which, I guess, includes any security flaws that may come up...
Google, you have 90 days to fix the Coronavirus - your time starts now!
"To avoid shipping flawed code"
A bit late for that, I feel.