Slashdot Mirror
Windows 7 Hits RTM At Build 7600.16385
An anonymous reader links to Ars Technica's report that (quoting) "Microsoft today announced that Windows 7 and Windows Server 2008 R2 have hit the Release to Manufacturing (RTM) milestone. The software giant still has a lot of work to do, but the bigger responsibility now falls to OEMs that must get PCs ready, Independent Software Vendors (ISVs) that are testing their new apps, and Independent Hardware Vendors (IHVs) that are preparing their new hardware. The RTM build is 7600, but it is not the same one that leaked less than two weeks ago (7600.16384). We speculated that Microsoft may end up recompiling build 7600 until it is satisfied, but it only took the company one more shot to get it right: 7600.16385 is the final build number. Microsoft refused to share the full build string, but if you trust leaks from a few days ago, it's '6.1.7600.16385.090713-1255,' which indicates that the final build was compiled over a week ago: July 13, 2009, at 12:45pm. This would be in line with the rumored RTM date but it is also the day Microsoft stated that Windows 7 had not yet hit RTM. Although the final build had been compiled, Microsoft still had to put it through testing before christening it as RTM."
Only 2 more service packs until it's stable.
but it only took the company one more shot to get it right
Really?
Can I have a rain check on that?
Beer is proof that God loves us and wants us to be happy.
Does this mean that they run the clock 10 minutes fast on the build machine to make them feel like they are ahead of the game ?
Nullius in verba
The testing has been around since Windows 7 Alpha, people payed to be on the bug testing team by buying this thing called Vista.
Anything can be found funny, from a certain point of view.
In America, Microsoft tests you.
Please do not read this sig. Thank you.
Anyone worth half a karma point here will recognise 16384 as a power of two.
In my years of software development, numbers like this jump out at you, usually while debugging something that has crashed due to overwriting something, and suspicious powers of two just scream 'BUG' at me.
Perhaps this move to manufacturing has simply been caused by microsoft not allocating enough bits in the build number, and one more recompile has tripped the manufacturing release...
struct BuildNumber
{
int IncrementalVersion : 14;
int ReleaseToManufacturing : 1;
int FinallyBugFree : 1;
}
(and if this really is the source code, we'll have to wait until release 32768 for a bug free version, assuming we don't hit -32768 first)
Windows 7 hits, RTFM
There, fixed that for you.
#DeleteChrome
Microsoft has actually addressed this before. Many applications pay attention to the major version number and refuse to work if they don't get something they recognize, so to retain compatibility, they bump the minor version. They did the same with Windows XP. This is the reason they gave in developer blogs, anyway.
Hard to do before they RROD... QQ
Actually, Internet Explorer 8.0 is a pretty good browser--I've seen a lot o stability improvements over IE 7.0 under Windows Vista Home Premium (SP2). I'd like it to be a tad faster, though.
As a web developer, I can tell you that IE 8 *does* compete very well with Firefox ... v1.5. It's standards support was outdated before it started development. And it's interface! Gag. IE 3 had a better interface. :(
"Microsoft has greatly approved their testing process..."
I don't doubt they have greatly "approved" it. Whether they have improved it is another matter.
I am sure that there are many other solipsists out there.
If the driver model was the same I would be able to load Creative Audigy 4 drivers for Vista without any issues.
----- You know you have ego issues when you register a domain in your name.