Slashdot Mirror
Windows 7 Hits Build 7600 (Possible RTM)
An anonymous reader writes "One Microsoft Way is reporting that Microsoft has significantly incremented the build number of both Windows 7 and Windows Server 2008 R2: 'Reports across the Web are pointing to a build 7600 for both Windows 7 and Windows Server 2008 R2. This is significant because the bump in the build number would suggest that Microsoft has christened this build as the Release to Manufacturing (RTM) build. The RTM is expected to be given out to Microsoft partners sometime later this month and launched on October 22, 2009, the day of General Availability (GA). The build string is "7600.16384.090710-1945," which indicates that it was compiled just a few days ago: July 10, 2009, at 7:45pm. Microsoft only increments the build number when it reaches a significant goal, and the only one left is the RTM milestone. The last builds that were leaking were all 72xx builds, so such a large bump is suspicious but at the same time it is something Microsoft would do to signify that this is the final build.'"
"As Microsoft strives to migrate their core technologies from the desktop onto the Web, so too is their propaganda machine migrating from the established press to the informal social web. Microsoft shills are invading social web sites everywhere - in forums, discussion groups, comments to news items, edits to Wikipedia, manipulation of search engines, comments to blogs - posing as innocent participants to promote their agenda and counter wide spread complaints about their shady marketing practises. Even in the comments section of blogs by Microsoft employees on their own corporate site they employ sock puppets to say the things the author felt inappropriate to say directly. They race to place their shill postings at the top spot in the comments section of news and blogs, or perhaps they are given advance notice enabling them to do this where they are a sponsor. The evidence is here on Slashdot for all to see, without embellishments from me. What I say here is amounts to only a digest of hundreds of postings by others. A careful investigator can see for himself the evolution of discussions on Microsoft related issues, especially those accusing them of their usual hard ball tactics. As one reads from Slashdot's historical record on through to recent times, the evolution of Microsoft's efforts to pervert Slashdot's discussions becomes readily apparent. Microsoft's ambition is to twist internet discussions around a full 180 degrees until these discussions become a platform for propaganda from Microsoft's "Ministry of Truth". A study of the comments of the shills posted here can be cross-correlated with postings on other sites. Their pattern of saturating a discussion with shill postings, and the repeating of mindless memes becomes obvious. Their harassment, ridicule, and suppression of criticisms is designed to intimidated those who would speak out against them. They seek to establish and enforce a discipline of giving Microsoft "fair treatment" and their propaganda the same consideration and respect a real person would deserve. In the process they are destroying Web 2 as we know it. This insidious attack on the infrastructure we rely upon to form our opinions in a complex world has both a direct and an inhibitory effect on free speech as a side effect. We must stop this while it is in its infancy. Once it fully established, it will become much more difficult to root out, and other ruthless corporations, organizations, and even governments will want to emulate the success of Microsoft's campaign. This is the nightmare vision of the end of the social internet as we know it."
http://news.slashdot.org/comments.pl?sid=1284651&cid=28502473
I enjoy a pro-Linux article as much as anyone else. Usually I'll give them my vote, but what turns me off on a Linux article is when the author tries to promote Linux by throwing negativity at Microsoft. If we ever want Linux to be an actual threat to Microsoft, it has to stand on its own, and not just be an alternative to Windows. Whining about your position in the market will do nothing to improve it.
It does seem like this may be the RTM build, although the timing is a little early yet.
My first reaction was the build number 7600 is very similar to the XP build of 2600 (yeah, I'm grasping at straws here.) It would be in MS favor to strongly relate this to XP and try to distance themselves from refencing Vista, which the correlation I just noted might help backup in people's minds.
However, the timing is just a little too early. The stated general retail release date from June's Computex is October 22. Historically, a MS OS RTM is released 30-45 days prior to the general retail date. That would place the RTM as beginning of September at earliest. Even a generous 60 day RTM date would place the date in mid-August, a month from now. Pressing and stamping aside (and what's to say a RTM DVD can't be downloaded over the net from a registration server similar to how volume and open license customers can already do), that's a little early yet.
And can anyone draw any significance from 16384 being 2^14? Or would that just indicate something like the 14th build of the master OS?
Build numbers by Microsoft follow an algorithm that encodes some odd information. Usually, it's desired by Microsoft to have a simply power of 2 for significant build milestones, especially for RTM builds. Why skip build numbers? That way you can still make builds of previous versions for commercial support, in order to make available patches for say, RCs and Betas, which both have a support lifetime as well. (Crazy short lifetimes, but they do.)
Messing with version numbers is a crazy stupid wrench in the "smooth" gears of the build system, and it requires authorization from significant master project managers. They would NOT be doing this if they were not important.
RTM builds also happen fairly early for things, especially because they have to have the RTM build, before they can complete localization, which means that if they want a synchronous release across X number of languages, they need to complete the RTM early enough that each of those localizations will be complete on time. Some of the localizations are just left for a late release anyways. But Japanese and German being Tier 0 languages pretty much means that they are important major goals to get as close to synchronous release as possible.
More interestingly is that this build was started at 7:45pm on a Friday... The build takes about 14 hours to complete, so someone was on call the whole weekend for completing the build... which potentially could have even TAKEN all weekend...
I think this is all just a really round about way of saying it, but "I. HATE. SAUERKRAUT!" No, really, you're totally on to the build number being of the form 2^x, but not that 14 has any significance to the build itself.
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
Nice comment. One question: How do you know how long it takes to build windows? Is it public information? or do you work for Microsoft?
I worked for Microsoft. I'm actually one of the few people who have compiled Windows.
They may have improved the build time since I worked for them, but the build times were a monotonously growing function of time when I left...
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS