New
#520
If ever! From my vantage point, I'd say it was a flop; only one or two "Skip Ahead" versions released before it was merged with the Fast Ring.
I opted in, but after a bit, I realized I wanted to stick with the Fast Ring on the Fall Creators Update in case I should find a bug. I didn't, but I could have . . .
The bottom line is that I finished out the testing of the FCU, and quickly caught up with those who got early Builds of the next version. I don't think I missed all that much, if anything at all.
Hmmm, d'ya think anyone has ever heard of, ". . . much ado about nothing"?
Yes, when it comes to the core Windows OS, but are you certain also Inbox Apps will be exactly the same at all times? Right now they might be but later I think they will lock in a specific version on Fast Ring while Skip Ahead will keep getting the latest version. Maybe this it's the case already. I would not know as I don't have a Fast Ring computer active at the moment.
Update:
#WindowsInsiders: there are no new builds today. We'll snap tonight's build as a candidate and see about mid next week.Tweet
— Twitter API (@user) View on Twitter
Given the volsnap.sys issue has over 300 upvotes, there seems to be an oxymoronic deafening silence from MS on this.
I am sorry but there is a big difference between a Windows build and an Inbox App. If you look really closely at all Inbox apps, their versioning has nothing to do with the Windows versioning.
For instance, we don't have OneDrive Build 17017.1000, or do we? This is were the difference could be. It is a bit unclear if MS will separate those parts between Fast Ring and Skip Ahead. For me it would make much sense to do it this way, because while Windows core binaries get new features, some Apps that are known to be good should be version locked until they break because something in the core OS changed too much. Meanwhile Skip Ahead would already have a working version and that version could be bundled in the Fast Ring and Slow Ring builds.
Just a thought.