There’s a lot of speculation about Windows 7 right now but specifics are a bit thin on the ground. Aside from the Engineering Windows 7 blog (which is information rich but makes some of my blog posts look short), as I said last year, pretty much the best place to watch right now is Paul Thurrott’s Windows 7 FAQ (Michael Pietroforte has an synopsis for IT administrators). Come PDC and WinHEC and the ‘net will be awash with Windows 7 news as that’s when developers and journos will finally get their grubby mits on a pre-release version of Microsoft’s latest operating system.
There has been some official news this week though. Yesterday, Mike Nash, Corporate Vice President for Windows Product Management at Microsoft, announced on the Windows Vista blog that the Windows 7 codename will not just be the codename but will also be the actual name for the next version of Windows (I understand that relates to the Windows client operating system and that Windows Server 2008 R2 will be the name for the server release):
“Over the years, we have taken different approaches to naming Windows. We’ve used version numbers like Windows 3.11, or dates like Windows 98, or ‘aspirational’ monikers like Windows XP or Windows Vista.”
OK, I get it. And Windows 7.0 would make sense for a major update (as Mike explained today in a follow-up post, but I’ll provide a few more details here):
- Windows 1.0 and 2.0 (Windows 286) existed as products but were not widely adopted.
- Windows 3.0, 3.1 (codename Janus), Windows for Workgroups 3.1 (codename Kato) and 3.11 (codename Snowball) were the first widely adopted versions.
- At that time the OS forked and Windows NT (New Technology) was born at v3.1, then 3.5 (codename Daytona), 3.51 (all minor release updates).
- The original Windows (not NT) 4.0 (codename Chicago/Detroit/Knoxville/Nashville) was called Windows 95 (and there were several variations of this operating system).
- Windows NT 4.0 (codename Cairo) was the first major update for Windows NT.
- Windows 98 (codename Memphis) and ME (Millennium Edition) were minor updates from Windows 95 (still 4.x) and then someone saw sense and closed down that product line, merging the codebase back into NT.
- Windows NT 5.0 was marketed as Windows 2000 (a major update).
- Windows NT 5.1 (codename Whistler) was marketed as Windows XP (a minor update).
- Windows NT 5.2 was marketed as Windows Server 2003 (codename Whistler Server) and Windows Server 2003 R2.
- Windows NT 6.0 (a major release) was marketed as Windows Vista (codename Longhorn) and Windows Server 2008 (codename Longhorn Server).
So far, this all makes sense (at least to me)… but then Mike Nash announced that:
“We decided to ship the Windows 7 code as Windows 6.1 – which is what you will see in the actual version of the product in cmd.exe or computer properties.”
So, Windows 7 (codename Blackcomb/Vienna/7) will not be v7.0 (indicating a major release) but will actually be 6.1 (i.e. a minor release). Based on recent history that really ought to fit with a Windows Vista R2 (marketing disaster waiting to happen), Windows Server 2008 R2 or Windows 2010 name. Nash continues by highlighting that:
“Windows 7 is a significant and evolutionary advancement of the client operating system. It is in every way a major effort in design, engineering and innovation. The only thing to read into the code versioning is that we are absolutely committed to making sure application compatibility is optimized for our customers.”
So, Windows 7 will be more like the move from Windows 2000 to Windows XP/2003, a significant step forward but still not a major update (unlike NT 4.0 to Windows 2000, or XP/2003 to Vista/2008). That’s good – especially for corporate IT departments struggling with Vista application compatibility (mostly through their own lack of foresight it should be noted). I understand why it’s numbered 6.1 internally but why confuse the issue by calling it 7 for marketing purposes?
I have a feeling that Windows 7 will not, despite yesterday’s announcement, be the final product name.