Understanding how Windows 7 Build numbers work
The development of Windows 7 has been exciting and relatively easy to follow, but a branch in the Windows 7 code base has recently caused a lot of confusion around the build numbers. The common misconception is that a larger build number means that the build is more recent than a build with a smaller number. Due to the recent branch in code base, this is no longer the case. The good guys at Icrontic have put up a very detailed post documenting on how to understand build numbers and the branching of the code base during development.
Branching Windows 7
You have undoubtedly noticed that all the builds up until this point have come from the 70xx.0.winmain line, so you’re wondering where this 7106 build came from, and you’re probably wondering if it’s better than 7077. Here’s the hard fact: It’s not.
When a project enters the code escrow phase, a development team can no longer afford to experiment with code changes when they only have one copy of the code (the winmain trunk). Bug fixes are not guaranteed to fix a bug, and they’re perfectly capable of spawning their own problems. So if Microsoft can’t afford to experiment with bug fixes on the winmain line, what can it do? It branches the code base.
A branch is a body of code created as an offshoot from the trunk of the development tree. This is different from a fork where the new project follows its own development path and may end up entirely different from the results of trunk development.
As a result Microsoft branching the Windows 7 project, it now has two parallel developments:
winmain_win7rc (Windows 7 build 70xx)
winmain (Windows 7 build 71xx)
As of now, this is how the builds are pegged to each other in each of the branches:
Build 7075.winmain (April 1) = 7105.winmain [April 4]
Build 7076.winmain (April 2) = 7106.winmain [April 8]
Build 7077.winmain_win7rc (April 4) = 7107.winmain [April 9]
To get a better understanding of build strings and how the Windows 7 branch operates, you can read the entire article at Icrontic.
Related posts:
Tags: windows 7, windows 7 build numbers, windows 7 builds, windows 7 RC, windows 7 RTM
To discuss this topic, head on over to our forums!
7 Responses to “Understanding how Windows 7 Build numbers work”
Leave a Reply
To discuss this topic, head on over to our forums!
Loading ...
Благодаря Ви за точната информация!Ползвам тази OS /Windows 7/ вече 4 месеца и съм възхитен от цялостната работа на системата. Ще се радвам окончателната версия да се появи скоро и ще я ползвам с удоволствие . С уважение към целия екип .
What?
It is Ukrainan. I do not know why he has written in Ukrainan here but I do know that he sad “Thanks” for the article. So do I.
I am Russian. Our languages (with Ukrainan) are similar (as, for example, Potugese and Spanish).
He is not Ukrainan he is Bulgarian, and he said:
Thank you for the correct information! Use this OS / Windows 7 / already 4 months and I admire the overall operation of the system. I’ll be happy final version to appear soon and will use it with pleasure. With respect to the whole team.
And I am Macedonian our languages are very similar with the Bulgarian
Thank you for the correct information! I use this OS / Windows 7 / already 4 months and I admire the overall operation of the system.I’ll be happy final version to appear soon and will use it with pleasure. With respect to the whole team.
[...] Understanding how Windows 7 Build numbers work The development of Windows 7 has been exciting and relatively easy to follow, but a… [...]
Hello,
We are working as a small group of development, test and analysis teams in my company using the Microsoft TFS.
And versioning has changed with branching ability of this tool for MS developers.
Thanks for your detailed explanation.