Microsoft puts the post-Vista wheels in motion

Microsoft puts the post-Vista wheels in motion

Summary: Windows Vista is not fully baked, but that doesn't mean senior management isn't already thinking about "Vista+1" as they like to call the next Windows client release (the one I believe is -- or at least was -- code-named "Fiji."

SHARE:
TOPICS: Windows
0

Windows Vista is not fully baked, but that doesn't mean senior management isn't already thinking about "Vista+1" as they like to call the next Windows client release (the one I believe is -- or at least was -- code-named "Fiji").

Microsoft has not yet built or tested even a pre-alpha version of "Vista+1," said Senior Vice President of COSD Jon DeVaan. Instead, DeVaan and his team have been focused on setting the priorities for COSD for the post-Vista and post-Longhorn-Server releases of Windows.

On October 12, DeVaan announced internally the reorganization of COSD, the team that develops the core of Windows client and server. The bottom line goal for the division, going forward: "We need to simplify the (Windows) environment to be more agile than in the past," DeVaan summarized.

COSD, which Microsoft created in December 2003 to insure "engineering excellence," is getting a few new branches. Specifically, COSD will now include new hardware and security teams. And the core architecture team, formerly led by Rob Short (who is currently on leave but expected to return, according to the Softies), has a new top dog. In the newly reorg'd COSD, the reporting structure now looks like this:

* The Windows Core System Team, led by Ben Fathi (Development), Darren Muir (Test) and Chuck Chan (Program Management) will be responsible for the Windows Core System, in the areas of kernel, virtualization, security, networking and deployment. Specifically, the former Trustworthy Computing Group that reported through Craig Mundie’s organization has merged with the Security Technology Unit that was under Ben Fahti’s leadership. Charny now leads this group and Fathi gets moved into Windows development.

* The Windows Engineering System and Services Team, led by Wael Bahaa-El Din, is responsible for the Windows engineering system, "delivering higher agility and productivity for engineering, as well as delivering a higher quality Windows System for customers," in Microsoft PR's own words.

* The PC Hardware Team, led by Jawad Khaki, will be responsible for working closely with OEMs, ODMs and IHVs.

* The Trustworthy Computing Team, led by Scott Charney, will spearhead everything from Trustworthy Computing to security engineering, security response infrastructure and security outreach.

* The Windows Core Architecture Team, under Richard Ward, "will focus on the Windows architecture, growing technical design across COSD and Windows, as well as growth and alignment of the COSD and Windows architect community."

Where does Windows Live fit into COSD's cross-divisional focus? After all, Windows is part of the broader Microsoft Platforms and Services division, which encompasses Windows, Windows Live, MSN and more. (And DeVaan reports directly to Platforms and Services chief Kevin Johnson.)

DeVaan said Microsoft will continue to hone Windows' role as a datacenter platform capable of support all of the "Live" services across the company, going forward. But there's no Live team that is part of COSD, per se.

Topic: Windows

About

Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

0 comments
Log in or register to start the discussion