Why didn't Microsoft change the version number from what we have on Redstone 2? I am quite aware we don't need to see any feature or differences from the Creators Update but the failure to change the version number while changing the build number is discouraging to me. I would have to keep my fingers crossed having seeing it been taunted as RS3 by ZDnet, Tharrutt and Neowin websites.
That part is not addressed in the OP. If I can recall correctly the OP is linked to the Windows 10 blog which never stated any reason for such discrepancy rather than we are to expect what occurred to previous transition process. I am not sure the version number was the same thing with previous Redstone 1, with regard to that change in that particular time. Can somebody really explain the version number?
Ok. Agree with your view but it is what I signed for. In other words, I am expected to install it irrespective of the bugs as an Insider in the fast ring.
The sole purpose of the Insider program is to have public beta tests of code changes. This means that there will be builds that are worse than others, there is no such thing as 'the perfect build', and due to its nature it's probably not the best sticking to a particular version just because it 'feels' better to use. The only time that you would steer away from a particular build is if you strike showstopper bugs, in which case you should provide feedback. If you aren't an Insider and just want the builds, it's kind of defeating the purpose and you are basically guaranteed to always run into problems. In terms of the version number 1703, it simply means 2017 month 3, so March 2017. If you changed this for the next Insider build, it would be 1704, but there's really no need because it isn't a public build. They could call it duffle monger, it wouldn't make any difference apart from the public not wanting something whose version is duffle monger. Apparently Microsoft are hoping for a November release of Redstone 3. If this holds true and it is finished in late October, it will have a build number 1711. That does signify that it is supposedly noticeably different to 1703. With Insider builds, a change of a month and build could simply mean a minor change, but if they continually changed it, it would get the new month's build number. That doesn't make much sense. Changing the build number does though, as well as the build string. The 1703 therefore is just for public identity, a very much simplified way of identifying the version, not using the build string like 16170.rs_prerelease.170331-1532. I bolded the yymm in the date stamp of the build, using the version number logic the Insider build would still be 1703 anyway!
That version number explanation is understandable. Can you specifically direct me to where the RS3 is embedded or written in this build? I really want to come to term with all the questionable information surrounding this build as Redstone 3. I like something I can easily defend in presence of my friends or mates, sir.