6 ms·

Changes to Chrome OS’s release cycle

42 points by feross 5y ago

yjftsjthsd-h 5y ago
So they're moving up the Chrome OS release pace to match Chrome itself. Really, the only surprise is that they didn't do that right away (hence having to make a slight correction to get them back in sync).
- jasonvorhe 5y ago
  Possibly because of the ongoing work of replacing the Chrome browser from Chrome OS with the Linux one.
  - nvllsvm 5y ago
    First I'm hearing of this. Have any links explaining more?
    - travisby 5y ago
      This has been referred to as [Lacros](https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/lacros.md https://chromium.googlesource.com/chromium/src.git/+/refs/he...) [aboutchromebooks](https://www.aboutchromebooks.com/news/lacros-vs-chrome-and-chrome-os-on-chromebooks/ https://www.aboutchromebooks.com/news/lacros-vs-chrome-and-c...) has a nice explanation as well. The reasoning I've read behind it is this will allow updates to continue for the browser much longer (probably more important!) than the cycle of the OS which has a much more finite support window.
bla3 5y ago
"To prepare for the 4-week release cycle starting in M96, we'll move from our current 6-week release cycle to a 10-week release cycle for M95." Sounds funny, but stuff happens :) Seems like a good thing to match the chrome cycle.
diogenesjunior 5y ago
i've enjoyed the addition of linux beta to chrome os
john2010 5y ago
I would love if there is RHEL equiv. chromeOS even for non-enterprise.
crazygringo 5y ago
I love browser auto-updates, but for at least half a year now every time Chrome updates on my Mac, I'm forced to re-grant location permissions in System Preferences. And they still haven't fixed it. Plus, certain financial institutions require me to go through lengthy 2FA again because I'm no longer using the "same" browser. (This is the fault of the institutions, not Google.) Again, auto-update is great, but there are still these little kinks that need ironing out... after so, so many years.
- abraham 5y ago
  Having to grant location permissions after Chrome updates might be fixed. I previously had the same issue but the latest update was fine.
  - crazygringo 5y ago
    Sadly, I just updated to 91 today, and just had to re-check location permissions yet again. I was so hoping you were right! Oh well...
- bla3 5y ago
  > after so, so many years. The location permissions system preferences behavior changes in more macOS updates than not. The current system hasn't been around for that long.

42 points by feross 5y ago

So they're moving up the Chrome OS release pace to match Chrome itself. Really, the only surprise is that they didn't do that right away (hence having to make a slight correction to get them back in sync).

jasonvorhe 5y ago
Possibly because of the ongoing work of replacing the Chrome browser from Chrome OS with the Linux one.
- nvllsvm 5y ago
  First I'm hearing of this. Have any links explaining more?
  - travisby 5y ago
    This has been referred to as [Lacros](https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/lacros.md https://chromium.googlesource.com/chromium/src.git/+/refs/he...) [aboutchromebooks](https://www.aboutchromebooks.com/news/lacros-vs-chrome-and-chrome-os-on-chromebooks/ https://www.aboutchromebooks.com/news/lacros-vs-chrome-and-c...) has a nice explanation as well. The reasoning I've read behind it is this will allow updates to continue for the browser much longer (probably more important!) than the cycle of the OS which has a much more finite support window.

bla3 5y ago

"To prepare for the 4-week release cycle starting in M96, we'll move from our current 6-week release cycle to a 10-week release cycle for M95." Sounds funny, but stuff happens :) Seems like a good thing to match the chrome cycle.

diogenesjunior 5y ago

i've enjoyed the addition of linux beta to chrome os

john2010 5y ago

I would love if there is RHEL equiv. chromeOS even for non-enterprise.

crazygringo 5y ago

I love browser auto-updates, but for at least half a year now every time Chrome updates on my Mac, I'm forced to re-grant location permissions in System Preferences. And they still haven't fixed it. Plus, certain financial institutions require me to go through lengthy 2FA again because I'm no longer using the "same" browser. (This is the fault of the institutions, not Google.) Again, auto-update is great, but there are still these little kinks that need ironing out... after so, so many years.

abraham 5y ago
Having to grant location permissions after Chrome updates might be fixed. I previously had the same issue but the latest update was fine.
- crazygringo 5y ago
  Sadly, I just updated to 91 today, and just had to re-check location permissions yet again. I was so hoping you were right! Oh well...
bla3 5y ago
> after so, so many years. The location permissions system preferences behavior changes in more macOS updates than not. The current system hasn't been around for that long.