New
#540
There is a big difference indeed. I guess some people can’t accept the fact that this isn’t Gram and Gramp’s Windows anymore. Hasn’t been since the inception/introduction of 8 with the Store app, UWP apps, and now Win32 app packages being offered through the Store. e.g. The new Office 365 Home preview.
Installation Package (Windows)
This is in no way the same as a win32 app developer tweaking their app and/or adding features, then sending it to update within the app via an installer.
Although the tree trunk (build) is the same ATM, the branches are still separate (rings). Skippy is a variant of the fast ring that accepts a higher risk. That’s why newer versions of apps get ported there. All Insider systems are registered on a server with their separate branches. MS controls the packages. Again, although the build is the same ATM, MS sends different packages to their respective Insider branch for testing. When they feel confident that they’re ready for fast ring, they’ll port them there. We also have to keep in mind other developers that need to tweak their apps.
Also, I’m sure MS is well on their way developing rs_5 and testing core apps on it as they go along. Both teams working in conjunction of one another. When they feel confident that rs_5 is ready, then they’ll port it over to Skippy for us to test. Meanwhile all those tested older versions of the apps stay with rs_4 to eventually get RTMed for the Spring/Summer Feature update.
Bottom line is that Skippy is very much alive. Just not in the magnitude that it was when rs_4 was introduced.