![]() ![]() Test on Dev and Beta ahead of the stable release that matches the upcoming LTC channel release.To keep system administrators and developers in alignment with the long-term support lifecycle, you should: LTC and LTS are designed to considerably reduce testing efforts for admins, while ensuring a secure operating system experience. We recommend keeping the majority of your devices on the LTS channel and use LTC to test the upcoming LTS release. Finally, switch your managed devices to the LTS or LTC channel from the Admin console. You can sign up for a Chrome Enterprise Upgrade trial to get access to the Google Admin console allowing you to setup and deploy managed Chromebooks . To enable either channel, you must have a Google domain and a managed device . In addition to operating system features and bug fixes, firmware updates are also bundled inside LTS releases up to a device’s auto update expiration (AUE). Devices left on LTC after LTS is released will also continue to receive security fixes every two weeks, and will automatically update to the next LTC release when it’s cut.Once LTS is released, it will continue receiving security fixes every two weeks.This means that 3 months after the initial LTC release, LTC will mirror LTS. LTC starts to receive security fixes every two weeks for the next 3 months until the next LTS release (108 LTS in the diagram).The LTC release (108 LTC in the diagram) is cut from the stable release (108 Stable), so during the first month both are identical.The LTC / LTS lifecycle works as follows: Except for a few users that should remain on LTC for testing purposes, most should be on LTS when adopting long-term support releases across an organization.ġ 0 2 L T S 108 L T S 105 S t a bl e 106 S t a bl e 1 0 7 S t a bl e 108 S t a bl e 109 S t a bl e 110 S t a bl e 111 S t a bl e 1 1 2 S t a bl e 113 S t a bl e 114 S t a bl e 1 1 5 S t a bl e 1 1 6 S t a bl e Sep 2 0 22 O c t 2 0 22 N o v 2 0 22 D e c 2 0 22 Jan 2 0 23 F eb 2 0 23 M ar 2 0 23 A p r 2 0 23 M a y 2 0 23 J un 2 0 23 J ul 2 0 23 A u g 2 0 23 S t a bl e C h annel 4 w e ek c y c l e L o n g T erm C and id a t e 3 m o n t h p r e v i e w L o n g T erm S t a bl e 6 m o n t h c y c l e 108 L T C 114 L T Cġ: Timeline of stable, LTC, and LTS releases Long-term support channel (LTS) - updated every 6 months, this channel has the slowest release cadence and is meant as a replacement for the normal stable channel.Long-term support candidate (LTC) - used as a basis for the next LTS version and is cut from Stable three months before LTS, giving admins a preview to prepare with.Both admins and developers should get familiar with them to provide a great experience to organizations adopting them.ĬhromeOS offers two long-term support releases: a long-term support candidate (LTC) release and a long-term stable (LTS) release. ![]() Long-term support releasesĬhromeOS’s long-term support releases are a powerful tool to reduce the effort to manage devices in an organization and certify that apps work well for every OS update. To provide better support and give everyone more time to test, we’ve created a new long-term support plan, with long-term support channels, for ChromeOS. Beta gives you a 4–6 week preview of features coming to Stable.īut, testing on a monthly basis with these existing channels can be challenging for system administrators and developers to keep up with. This build is still subject to bugs, but gives a 9–12 week preview of what’s coming to Stable. ![]() Dev gets updated once or twice weekly, and shows what the Chrome team is working on right now. ![]() Developers can test their applications on the developer (Dev) or beta (Beta) channels before each new stable version is released, to make sure their apps work well. Minor updates, such as security fixes and software updates, happen every 2–3 weeks. By default ChromeOS releases a full OS update to the stable channel (Stable) about every 4 weeks. Frequent operating system updates are vital to ensure security and access to the latest features. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |