topic Re: Auto-Update Settings During State Testing Window in Peer-Peer Topics

Auto-Update Settings During State Testing Window

Scott_Kovis — Wed, 17 Apr 2024 14:22:48 GMT

Hi all. I feel like there was a post or three in the old Currents forum about this, but I didn't find anything here after a quick search...

Where do we stand as far as pausing Chrome OS updates at the current 123.* version during the state testing window over the next four weeks? While latest update is obviously safest in the long-run, it seems there were some who limited updates to the latest stable version so that testing didn't experience any OS update-related problems.

What say you? Thanks in advance for your wisdom!

Cheers,
Scott

Re: Auto-Update Settings During State Testing Window

9330cashmore — Wed, 17 Apr 2024 15:29:36 GMT

We held ours to the LTC since that is what our vendor said they would support.

Re: Auto-Update Settings During State Testing Window

steve — Wed, 17 Apr 2024 15:48:39 GMT

Probably a good idea, less chance of surprises!

Re: Auto-Update Settings During State Testing Window

bethhughes — Wed, 17 Apr 2024 19:41:46 GMT

Our student device OU is set to 114 (long-term support channel) per test vendors' tech specs.

Re: Auto-Update Settings During State Testing Window

MattDPenn — Thu, 18 Apr 2024 16:52:42 GMT

We're holding fast to LTS 114 for the moment despite LTS 120 recently becoming available as a "just in case" measure. Our testing program says it should be compatible with v108 and up but why take the chance? Either way I would highly recommend switching to the LTS channels as I don't know if Google's gotten better about breaking stuff with the latest "stable" builds but LTS channel was specifically made to avoid that headache and if a vendor isn't targeting LTS versions then I'd be wary irregardless.

Re: Auto-Update Settings During State Testing Window

mhermmsd — Thu, 02 May 2024 20:05:42 GMT

Most of our test vendors say they will support to the latest stable build so we usually just let them update to that. We usually just lock updates to the current version a couple weeks before testing begins.