Addressing the confusion around Windows 7 'build forking'

So there's been some silliness about the Windows 7 "build forking" stuff out in the blogosphere, which is to be expected. No one outside of Microsoft really understands how Microsoft creates Windows, but everyone seems to have an opinion about it for some reason, and some people even try to speak from a position of authority about how it's done. (Which I find odd, but whatever.) I tried to downplay this stuff on this week's Windows Weekly podcast because I don't think the process is necessary relevant from a conversational standpoint, whereas how Microsoft is changing the Windows experience is extremely relevant. But I had to address this issue in my Windows 7 build 7106 screenshot gallery because, obviously, it's confusing that builds are now jumping up and down between the 70xx and 71xx series.

As a follow-up, I heard from a Microsoft employee who's emailed me from time to time off the record about Windows 7. And I'd like to present an edited version of what he told me here, if only to address the confusion out there. What it boils down to is that Microsoft has been forking the build since Windows 7 development began.

This "forking" procedure is a bit different than before. The build number jump now is actually identical to the process followed for the Beta.

For the Beta, builds 6980-7000 (or so) were reserved for potential beta clients, while development went on ahead for build 7022 as the first post-beta pre-RC build at the same time.

It's not so much a "per-feature" issue Microsoft is avoiding here, working on individual features and slamming them all together in the end, but rather working towards a more stable public release.

Once into Beta "Lockdown", and then into Beta "Escrow", the bar for fixes gets extremely high. Only the most severe, important fixes are taken, fixes that have the least risk to the stability of the Beta.  Any riskier fixes are postponed into the post-beta builds (7022+) to help keep the Beta as stable as possible.

Now, the same thing is going on with RC - the bar gets really high for RC bugs, and anything that will be fixed for RTM, but might be too risky to fix yet for RC, goes into the 7105+ builds.

Hope this helps.

Discuss this Article 10

anonymous
on Apr 14, 2009
BEGINTRANSMIT Oh, silly, petty humanoids. I am reminded of a joke by Quegar the Disemboweler, upon the conquest and demineralization of the Tw'ill of Alpha Minor. He said, "Orange." We laughed and laughed like schoolgirls, and then began Revolutionary Assailment Protocol 47. I guess you had to be there. ENDTRANSMIT
j4m3s0n79
on Apr 14, 2009
fork you! sry...couldn't resist.
pthurrott
on Apr 14, 2009
Commander: That's exactly what I thought too! :) Oh, wait.
johnbaxter
on Apr 14, 2009
Now that that has been cleared up, we can safely move along. Each number is--a number.
DarkSages
on Apr 14, 2009
I just hope that what ever microsoft has up it's sleeve gets tested well before release.
yert
on Apr 14, 2009
Paul, any comments on what you think the final build number will be? I hear Bott thinks it's gonna be 7777.
mikegalos@msn.com
on Apr 14, 2009
yert, The guesses I saw on yesterday's conversation about this were: Ed Bott: 7777 Me: 7700 David Taraso (from JCXP.net): 7200 (None of us know what it will be but are making guesses based on likely numbers from past history of build numbers. The Windows team typically picks a meaningful number and jumpst to it for the final build so there's no assumption on the number of real builds before release, just that they'd pick these particular numbers.)
whiplash55
on Apr 14, 2009
I think they should dump the whole thing, rewrite it using .net. Ya that's the ticket!
Waethorn
on Apr 15, 2009
The magic question is: what will be the final RTM build number?
anonymous
on Apr 27, 2009
I still can't believe their so ontime for the RC release, Gone are the Vista days i guess.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• 120 Technical
Sessions
• Networking with Peers
• Expert Speakers


Come See Paul Thurrott & Mary Jo Foley in Person!

Register Now

Office 365 InfoCenter

Get the latest insight and info from Paul

Read Now!

What I Use