The first part of that solution is separating out the Chrome browser from Chrome OS and that’s currently in-flight with the Lacros browser see my explainer here. I still think that this integration can be the second prong of keeping older Chromebooks up to date with security patches and other Chrome OS updates. What might change after CloudReady becomes “an official Chrome OS offering” then is still anyone’s guess at least anyone outside of Google. Over the long term, CloudReady will become an official Chrome OS offering, and existing customers will be upgraded seamlessly as that happens To that end, at least we know that current CloudReady users won’t be impacted based on this statement provided on the day Google acquired Neverware:ĬloudReady will continue to be available as-is, and we’re committed to supporting and maintaining existing customers. So this effort doesn’t provide any insight into how CloudReady will be used by Google, nor what device support will be like. If it’s not yet clear, the integration process to merge CloudReady with Chrome OS is in the very early stages. The Beta Channel of Chrome OS 90 is pretty stable in my experience and is expected to release into the Stable Channel on or around April 20, which is just a few weeks away. There’s not much point in using Chrome OS 89 (the current Stable version) or less since there are new features in 90 and 91 that could require more integration work if ignored now. In the Chromium code repository, he has a shiny new email address.Īs far as which Chrome OS release these integration efforts are using, version 90 appears to be it. It’s also worth noting that one of the reviewers for these code changes is Nicholas Bishop, who appears on the Neverware team page as a Senior Software Engineer. In the coming weeks, I’d expect the code to be an “internal” repository inside of Google as opposed to an “external” one. That makes sense as a first step as Neverware has managed all of its code on GitLab since 2015.īut you can see by this code change that the code will be subsumed by Google’s internal Chrome OS code management tools for device builds. ![]() This particular comment had me researching the two code bases a little more and part of the integration is moving all CloudReady code into Google’s own code repositories. ![]() Indeed, the initial code and comments specifically note that some parts of the integration are “hacks” for now: To be clear, this is the first of what will likely be many integration steps. Now, Google is quickly working to integrate Neverware CloudReady into Chrome OS 90 for prototyping. Back in December, news hit that Google acquired Neverware, creator of the Chromium OS-based CloudReady software that can give new life to old laptops and Chromebooks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |