New
#280
I wrote a comment on that in the thread about build 16278:
https://www.tenforums.com/windows-10...ml#post1125285
I wrote a comment on that in the thread about build 16278:
https://www.tenforums.com/windows-10...ml#post1125285
This is natural in a build-up to final release... all channels are working on the same build and it's compile, test, fix, compile, test fix ...ad nauseam now - thus the fast increase in build version (whereas before each channel eg, Edge, Xbox etc only did component development on their specific builds) - they now need to test the integrated solution for FCU.
My worthless two Euro cents:
I simply do not understand the importance to know which build number will be the next one released to Fast Ring, which will be next public release, if it's 16xxx or 17xxx. It has none whatsoever affect in my Windows usage.
Whatever build will be released, I will get it regardless of what digits are used to describe it. I do not decide to get or skip a build based on its build number. Of all things Windows 10, the build number is the most unimportant. Last Slow Ring build released is current Slow Ring build, last Fast Ring build is current Fast Ring build, next general release will be Autumn (Fall) Update. All this regardless of which build numbers they have.
Well, major number shows which generation a build belongs to and with it possibility of anything new or will it be mostly bug hunting and fixing. Major number change may also mean soon appearance of public build. And than there's curiosity![]()
Curiosity about the inner working in Redmond is quite natural for those of us who have countless hours sticking with the Insider Program since the beginning. If it didn't mean anything at all why would Dona "leak" release build numbers on pieces of cake or whatever? :)
OK, a purely hypothetical scenario:
On some tech site, members keep guessing post after post about what will be the build of OS MacWinlux that might or might not be released today or tomorrow or next week. Will it be 29333 or 29401, or will it make a major jump to 30000?
Person responsible about the beta testing program at MacWinlux HQ in Chennai, India, Mr. Sana Dorkar then decides today we will release build 29401 because it's as ready to be released as it could be, internal testing showing it has no major bugs.
You as a participant in MacWinlux' beta program, having installed and tested each and every earlier build, will you now skip build 29041 because it was not the build you had guessed and were anticipating? Or would you download and install it regardless its build number?
Of course the build numbers are important but only as to separate different versions. As long as the new build number is greater than its predecessor, it really is completely irrelevant to us users which build will be released next. In any case, we will download and install it or upgrade to it.
Outside the pseudoscience numerology, there are no factual reasons to care about what the next build will be. It will be what it will be and we all will get it. Not a single of us Insiders skips a build because it has wrong number.
I am quit sick at the moment (physical, not because of this debate!), would like to write an essee about this but have to keep my posts short for now...
But wait. We just had MS back off a higher build number with a major version viz. 17000. Interestingly that build has now been removed from Build feed.
The following build - compiled last Friday will likely be the one we get this week. And yes if is not I will still download the next rs4 build.
10.0.16353.1000 (rs_prerelease.170825-1423)