Author Topic: Build 7100 is the assumed official Win7 RC1 build- Windows 7 Code base branching  (Read 2504 times)

Offline riso

  • Administrator
  • Hero Member
  • *****
  • Posts: 6413
  • Gender: Male
  • Beta tester Tech support dedicated 110%
    • windows 10 news and info | Forum - Blog
Windows 7 Build 7106 leaked earlier this week and there was a huge amount of excitement around the forums because of the obvious large gap between 7077 and 7106; seems like a lot of builds!

The truth is, they’ve just branched the code base this week; checking out build 7076, and relabelling it as 7106, ready to work on towards the RTM build, while 7076, 7077 onwards, will be polished to ultimately be released as the RC (probably) at build 7100.



So.. 7106 is actually 1 day older than 7077. Anyone thinking about rushing out and sourcing a chinese iso and a language pack can probably hold out for either the RC or a later RTM branch build,
riso
« Last Edit: April 16, 2009, 08:07:53 AM by riso »

Offline riso

  • Administrator
  • Hero Member
  • *****
  • Posts: 6413
  • Gender: Male
  • Beta tester Tech support dedicated 110%
    • windows 10 news and info | Forum - Blog
Re: Windows 7 7106 - Code base branching
« Reply #1 on: April 16, 2009, 08:02:28 AM »
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.

Offline Snuffy

  • Hero Member
  • *****
  • Posts: 381
  • Gender: Male
Very well stated.  I'm sure this will assist in the clarification to many members.  whom might other wise clammer all in a sweat for the illfated cn.7106.en-ru addon mess.

I so far am happy with v.7077 - EULAID:VISTA_RM.0_LIP_RTL_en-US
The only STUPID Question is the one you never asked.

Offline jychan28

  • Newbie
  • *
  • Posts: 39
I am not sure what really does that mean when people say they are happy with 7077.  I have installed the x64 version but I still can't get my Bluetooth stereo working.  It kept complaining no proper drivers and sent me to Broadcom website.  Sure enough Broadcom does not have it.

I can't see thumbnails with Explorer in Windows 7.  I can see icons but not thumbnails of jpeg files.  Windows XP of course has no problem with that.  When the jpeg filename is in Chinese, thirdparty viewers such as Farstone viewer or Maxviewer do not work.  They work fine with Windows XP.  I can't input Chinese in Windows 7 yet but no problem with Windows XP.

Microsoft gets to be more fascist, if you are using Firefor, it will tell you that your browser is not IE and deem to be unreliable and Microsoft may not display the page for you.

So far, I am dual booting Windows XP and Windows 7.  I don't think it is smart to jump into it even I have been using Windows 7 on and off for the last couple of months.

So far if people ask me what I found Windows 7 is better than Windows XP, I will just say it is newer.  New and latest stuffs got to be better than old things but please don't ask me to give examples or evidences to back up backup that statement with Windows 7.  I am sure if you asked Microsoft, they will say,"Trust me".  That will be all I can say.