This "information" was available yesterday. At this point - we don't have any concrete information on the daily builds being incremented by 16 and compiled in multiple branches, including th1. We have seen rumors and theories about what they might be, but nothing official. This chart that was published strikes me as nothing more than someone doing some basic math and discovering some coincidences that 10400 would be reached before July 29th. The fact that this information is being referenced by the same individuals that claimed July 9 was sign-off date speaks volumes to its credibility.
Can I just chime on this thread to say that watching you guys debating this is almost as entertaining as checking the thread for the confirmation of the actual RTM build number (And, yes, I realise the oxymoron) /raises_glass
RTM will be 10400 we have a while yet 10176 is RTM Escrow (Not final) There are a few builds atm newest i think is 10.0.10240.16384.th1.150709-1700 (not leaked)
**sigh**..another RTM candidate 10.0.10240.16384 At the rate they are going they may pass .400 before they get one they want to keep, then what with Redstone starting at 500?
What Wzor has posted is true (so far) Could they in theory pass 10240 say tomorrow and sign it off as Gold RTM and bump the number?
Sorry, what WZor posted was total baloney, he doesn't even know the difference between RTM escrow and RTM sign-off candidate(lmfao), The so-called rtm1/2/3 were just his fairy tales. build 10176 has the 15th bit as 1, it was a sign-off candidate, if not for some f**king app bug, it could have passed the sign-off test runs and signed by 2 MS big-shots and released to the manufacturing process. BTW, good news for guys who worried about win10 activation(i.e. if you are unable to get the win7/8.1 free upgrade, or if you like to use Enterprise), build 10176.16384 could be KMS activated just like win8.1, using the GVLK from MS. This build was a sign-off candidate, everything in it is final, unless a bug was found, then only those files concerning the bug would be changed for fixing the bug.