Recommended Posts

You guys do realise 7106 might seem newer then 7077 but it's not.. its just 7076 with an upped build number.. don't be fooled by MS moving build numbers up. So no point to download if you already have 7077 you will be downgrading.
Yes that's exactly right.
Yup, up to 7109.0.090413-1552 in winmain now....heating up ;)

Ok, then whats the "real" build number on that one? 7079?

Thanks M$, once again, for contributing to the general confusion :p

You guys do realise 7106 might seem newer then 7077 but it's not.. its just 7076 with an upped build number.. don't be fooled by MS moving build numbers up. So no point to download if you already have 7077 you will be downgrading.

I wrote a quick article on how they've branched the code base, with a little diagram. Anyone who's curious: http://www.blogitech.co.uk/2009/windows-7-...base-branching/

Chris

I wrote a quick article on how they've branched the code base, with a little diagram. Anyone who's curious: http://www.blogitech.co.uk/2009/windows-7-...base-branching/

Chris

Well that confirms what I thought, shall be waiting for the next build then. Thanks for the info

Ok, then whats the "real" build number on that one? 7079?

Thanks M$, once again, for contributing to the general confusion :p

That is the real build number. There is no confusion, unless you are an employee, you do not need to know this. Anything above Build 7100 is a winmain build. But because they have just split Windows 7 into two as they transition to the RC branch, the current winmain build is older than the current RC build. The RC builds have their code frozen, they will continue to become better, and they will strive to become bug-free builds, they will continue below Build 7100. From what I read, Build 7100 is the assumed official Windows 7 RC1 build. It has yet to be thought out and compiled, but the RC branch ends at Build 7100, so they can stop before Build 7100 and keep the RC1 build at Build 7095 or 7099, but most likely they will go all the way to Build 7100.

From what I understand, Microsoft will continue to make winmain builds, these builds will be much better because their code isn't frozen like the RC builds are. The problem with having a divided Windows 7 is the sync between them. The RC branch might be better for reliability and polished looks, but the winmain branch will have newer code and that means more stable. The point of the RC branch is to take the last winmain build and make it look prettier, no code is really changed, the builds will go higher and higher, but its the same winmain build from before except it is more refined everytime it is compiled as a new build. I'm assuming they sync the latest build from the RC branch with the latest build from the winmain branch, but because they are two different branches, the builds do not come out at the same time and so that is what throws off the winmain builds.

The winmain branch is newer than the RC branch, I will use a winmain build over an RC build any day except this one since it is just labeled a new winmain build, nothing different happened. The winmain builds come after RC and I think having newer code is better than having a little new effect unless a new UI is coming and they decide to throw it in the RC branch and the latest winmain build does not get that yet.

-------------

I only read the article once and I kind of got the idea, I did not reread 10 times, I only took what I read once and explained this to ThePitt, I might have said something wrong once or twice so I'm going to reread now. :yes:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Too soon, I'm still not over this death!
    • Normally, I admit when a title is clickbait (unfortunately, it's become somewhat necessary in AI-dominated news sections today), but in this case, all supported versions is implied and doesn't need to be spelled out in the title. Of course, I'm covering a Patch Tuesday update but that is only available to supported Windows SKUs. All our coverage relates to supported Windows software and SKUs only unless we expressly state that it's "unsupported", "unofficial", or "third-party". I'm sorry, but supported/official SKUs don't need to be spelled out as such in every Neowin headline.
    • ALL versions or ALL SUPPORTED versions? Neowin does it again.
    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      586
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!