In software development, especially in Google’s development cycle, it is common for developers to “eat their own dog food” before the average user tests, which is to use and test the results of their work. Google’s long-developed Fuchsia system appears to be in the “dogfood” phase, meaning development may be at an end and users will be invited to test it.
In addition to routine public testing such as Alpha and Beta, There are several rounds of internal testing during the development cycle of Google’s products, all of which include the “dogfood” suffix.
For example, in the early stages of development, Google Plus followed the project’s code name, “The Emerald Sea,” in a small “fishfood” test phase before performing a company-wide “dog food” test. The name fish grain has been around ever since, and other Google teams used it in the earliest testing phases.
In addition, Google sometimes has a slightly wider “team food” test ingress between fish and dog food, which is usually the last, almost company-wide, in-house test before bulk reproduction of production or social public testing.
Indications from the past year suggest that at least some of the modules of the Fuchsia system (if the entire system has not yet passed) have passed the “fish grain” and “team food” testing phases. The next stage of testing, of course, is “dog food”, which will allow Google employees to be invited to conduct more extensive testing of the Fuchsia system.
The recent code adjustment, which indicates that Fuchsia has entered the “dog food” stage. In one of the changes associated with Omaha, an update management system used by Chrome and Chrome OS, we saw developers test ingress with a pair of commands, one of which is more obvious.
The first command is “fx shell update channel set dogfood-release”. The command “fx shell” is similar to Android’s “adb shell” and actually passes the command to run on the device. The command primarily tells the Fuchsia device to use the “dogfood-release” update channel.
The second command simply tells the Fuchsia device to look for updates through “Omaha.” From this, we can see that Google has a “dogfood-release” update channel on which some developers have already started testing.
According to Google’s plan, Fuchsia OS will be able to run on desktops, laptops, tablets, laptops, phones, routers, smart displays, and more. This means that Google’s dog food tests will cover a variety of different hardware devices.
The third code change basically confirms that Fuchsia has entered the dog food stage. In a longer discussion about how the Fuchsia system update works, a Google employee shared two very interesting URL addresses, “Fuchsia-updates.googleusercontent.com” and “” arm64.dogfood-release.astro.fuchsia.com”.
The word “Astro” appears on a web address (arm64.dogfood-release.astro.fuchsia.com), which coincides with the name of a prototype device that Google installed in the early days of the Fuchsia OS system, which was later officially known as “The Smart Home Device”. Google Nest Hub.”