Development of Windows Vista
Development of Windows Vista, the planned next version of Microsoft Windows, occurred over the span of several years, starting in earnest in May 2001,[1] prior to the release of Microsoft's Windows XP operating system, and continuing into 2006. It was originally expected to ship sometime late in 2003 as a minor step between Windows XP and "Blackcomb" (now known as Windows "Vienna"). Gradually, "Longhorn" assimilated many of the important new features and technologies slated for "Blackcomb", resulting in the release date being pushed back a few times. Many of Microsoft's developers were also re-tasked with improving the security of Windows XP. Faced with ongoing delays and concerns about feature creep, Microsoft announced on August 27 2004 that it was making significant changes. "Longhorn" development basically started afresh, building on the Windows Server 2003 codebase, and re-incorporating only the features that would be intended for an actual operating system release. Some previously announced features, such as WinFS and NGSCB, were dropped or postponed.
After "Longhorn" was named Windows Vista in mid-2005, an unprecedented beta-test program was started, which has involved hundreds of thousands of volunteers and companies. In September 2005, Microsoft started releasing regular Community Technology Previews (CTP) to beta testers.
2002: Early development
The early development stages of the next version of Windows were generally characterized as being incremental improvements and updates to Windows XP. During this period, Microsoft was fairly quiet about what was being worked on, as their marketing and public relations focus was more strongly focused on Windows XP, and Windows Server 2003, which was released in April of 2003. Occasional builds of Longhorn were leaked onto popular file sharing networks such as IRC, BitTorrent, eDonkey and various newsgroups, and so most of what is known about builds prior to the first sanctioned development release of Longhorn in May 2003, is derived from these builds.
Most builds of Longhorn and Vista were identified by a label that was always displayed in the bottom-right corner of the desktop. A typical build label would look like "Build 3683.Lab06_N.020923-1821". Higher build numbers didn't automatically mean that the latest features from every development team at Microsoft was included. Typically, a team working on a certain feature or subsystem would generate their own working builds which developers would test with, and when the code was deemed stable, all the changes would be incorporated back into the main development tree at once. At Microsoft, a number of "Build labs" exist where the compilation of the entirety of Windows could be performed by a team. The lab in which any given build originated from is shown as part of the build label, and the date and time of the build followed that. Some builds (such as Beta 1 and Beta 2) only display the build label in the version information dialog (Winver).
Milestone 1
Build 3646 (built on June 12 2002) was the first known build of Longhorn. It had a build label of "Lab01_N(portbld).020612-1346", so it was quite likely a very early porting build from the Windows XP codebase.
Milestone 2
Build 3663 (build date of July 28 2002) was the first known build with leaked screenshots. It was the first sighting of the "Plex" style which Microsoft regarded as a place-holder theme for their development versions, until they were ready to demonstrate Aero. Screenshots of 'Build 3670 (build date of August 19 2002) also showed a variation of the Device Manager implemented inside Windows Explorer.
Milestone 3
Build 3683 (build date of September 23 2002) was the first build of Longhorn that was leaked to the Internet. This build was the first of several that had a working title of "Longhorn XP Professional". Visually it was not significantly different from Windows XP, incorporating aesthetic changes and a few new user interface options. A new "Sidebar" was also present, which contained many of the widgets that would much later be seen in Windows Sidebar, such as an analog clock, slide show, and search capability. An option in this version of the sidebar also made it possible to move the Start button into it, and disable the traditional taskbar entirely. An early revision of WinFS was also included, but very little in the way of a user interface was included, and as such it appeared to early testers to be nothing more than a service that consumed large amounts of memory and processor time. The "Display Properties" control panel[2] was the first significant departure, being built on the new "Avalon" application programming interface.[3]
Build 3706 was leaked in May 2006. It had some DCE/DWM features, and predates 3718, previously thought to be the first DCE/DWM build.
Build 3718 (build date of November 19 2002) was leaked two years after its build date. It included the Desktop Window Manager and Aero effects. As a demonstration of the DCE's capabilities, programs literally flipped into the taskbar and twisted as they were minimized.
2003 and early 2004: New technology
Milestone 4
After several months of relatively little news or activity from Microsoft with Longhorn, Build 4008 (with a build date of February 19 2003) made an appearance on the Internet around February 28 2003.[4] It was also privately handed out to a select group of software developers. As an evolutionary release over build 3683, it contained a number of small improvements, including a modified blue "Plex" theme and a new, simplified installer that operates in graphical mode from the outset, and completed an install of the operating system in approximately one third the time of Windows XP on the same hardware. An optional "new taskbar" was introduced that is thinner than the previous build and displayed the time differently.
The most notable visual and functional difference, however, came with Windows Explorer. The incorporation of the Plex theme made blue the dominant color of the entire application. The Windows XP-style task pane was almost completely replaced with a large horizontal pane that appeared under the toolbars. A new search interface allowed for filtering of results, searching of Windows help, and natural-language queries that would be used to integrate with WinFS. The animated search characters were also removed. The "view modes" were also replaced with a single slider that would resize the icons in real-time, in list, thumbnail, or details mode, depending on where the slider was. File metadata was also made more visible and more easily editable, with more active encouragement to fill out missing pieces of information. Also of note is the conversion of Windows Explorer to being a .NET application.
Milestone 5
Build 4015 (build date of March 28 2003) was also leaked to the Internet around the end of April 2003. A number of features Microsoft had been working on were rolled into this build, such as a range of parental controls, a lot of additional configurability for the sidebar (including being able to put it below the start bar at the bottom of the screen), and the notion of "Libraries" of files. Significant memory leak problems with Windows Explorer and the Sidebar made this build difficult to use, which resulted in some third-party hacks to mitigate the problem. The back-end database of Outlook Express changed completely, and became dependent on WinFS to store its email. WinFS itself still had significant performance and memory usage issues, and so it became common for testers to disable WinFS entirely, thus rendering Outlook Express inoperative.
At the Windows Hardware Engineering Conference (WinHEC) conference in May 2003, Microsoft gave their first public demonstrations of the new Desktop Window Manager and Aero. The demonstrations were done on a revised build 4015 which was never released. A number of sessions for developers and hardware engineers at the conference focused on these new features, as well as the Next Generation Secure Computing Base (previously known as "Palladium"), which at the time was Microsoft's proposed solution for creating a secure computing environment whereby any given component of the system could be deemed "trusted". Also at this conference, Microsoft reiterated their roadmap for delivering Longhorn, pointing to an "early 2005" release date.[5]
Build 4028 was the first leaked Enterprise Server build, based on Windows Server.NET RC1, which later became Windows Server 2003. Build 4029 (build date of June 19 2003), however, contained neither of these new technologies. Windows Explorer went through a number of other changes. Larger previews of images were displayed when the mouse hovered over an image file, column-level filtering of results was introduced, and overall performance of Explorer was somewhat improved over build 4015, though the memory leak issues were not entirely resolved. Batch image processing of images was also introduced, making it possible for a user to rotate a number of images at once.
Build 4029's name was displayed as "onghornLay rofessionalPay" (Pig Latin for Longhorn Professional) in various places around the operating system. While some had presumed that screenshots of this build were fake because of this seemingly obvious mistake, Microsoft later explained that this was merely a test of some new code to locate and reduce the number of places in the operating system code that the name was defined.[6]
Milestone 6
Build 4033, similar to 4029, but with some UI improvements, including an updated Plex theme.
Build 4051 (build date of October 1 2003), the Official PDC 2003 build. Not released to the general public, but it did leak in October 20, 2003. Introduced a new Slate theme.
Build 4053 (build date of October 29 2003) - Minor changes.
Milestone 7
Build 4074 (build date of April 25 2004) - Official WinHEC 2004 preview build. Introduced a new Jade theme.
Build 4083 (build date of May 16 2004) - The last leaked 64-bit XP-based build. Both Sidebar and WinFS were dropped from this release. Considered highly unstable, including the absence of programs in the start menu and driver and installation issues.
Build 4093 - The last leaked 32-bit XP-based build. Considered highly unstable. Contains Sidebar, WinFS, and Avalon-based Windows Movie Maker.
Mid-2004 to Mid-2005: Development "reset"
By the end of 2003, it had become obvious to the Windows team at Microsoft that they were losing sight of what needed to be done to complete the next version of Windows and ship it to customers. Internally, some Microsoft employees were describing the Longhorn project as "another Cairo" or "Cairo.NET", referring to the Cairo development project that the company embarked on through the first half of the 1990s, which never resulted in a shipping operating system (though nearly all the technologies developed in that time did end up in Windows 95 and Windows NT.[7])
In a September 23 2005 front-page article on The Wall Street Journal[8], Microsoft co-president Jim Allchin, who had overall responsibility for the development and delivery of Windows, explained how development of Longhorn was "crashing into the ground" due in large part to the haphazard methods by which features were introduced and integrated into the core of the operating system, without a clear focus on an end-product. In December 2003, Allchin enlisted the help of two other senior executives, Brian Valentine and Amitabh Srivastava, the former being experienced with shipping software at Microsoft, most notably Windows Server 2003[9], and the latter having spent his career at Microsoft researching and developing methods of producing high-quality testing systems.[10] Srivastava employed a team of core architects to visually map out the entirety of the Windows operating system, and to proactively work towards a development process that would enforce high levels of code quality, reduce interdependencies between components, and in general, "not make things worse with Vista".[11] These things, in conjunction with the fact that many of Microsoft's most skilled developers and engineers had been working on Windows Server 2003, led to the decision to "reset" development of Longhorn, building on the same code that would become Windows Server 2003 Service Pack 1, instead of the older Windows XP. This change, announced internally to Microsoft employees on August 26 2004, began in earnest in September, though it would take several more months before the new development process and build methodology would be used by all of the development teams. A number of complaints came from individual developers, and Bill Gates himself, that the new development process was going to be prohibitively difficult to work within. Changes at the build labs also resulted in a period of time of several months where no builds of Longhorn were leaked onto the Internet.
Longhorn "D1"
Build 5000 (build date of September 8 2004) is notable, as it was the first build of Longhorn based on the Server 2003 codebase, but with the Windows XP interface. Successive internal builds over several months gradually integrated a lot of the fundamental work that had been done over the previous three years, but with much stricter rules about what code could be brought into the main builds. Builds in this period of time were described variously as Longhorn "D1", and as Milestone 8 / 9, depending on whether the new or old build tree was being worked on.
Build 5048 (built on April 1 2005) was the official WinHEC 2005 preview build, described as the Longhorn Developer Preview, and made available to WinHEC attendees on April 24 2005. It was the only build from this time period that was made available by Microsoft; it was not officially distributed outside of WinHEC, but the build quickly appeared on file sharing networks. The Aero visual style made its first appearance in this build, and the Desktop Window Manager was present but disabled and hidden by default. At the keynote presentation, Bill Gates also announced that many of the WinFX developer APIs that were originally planned exclusively for Longhorn were going to be backported to Windows XP and Server 2003, and that the final user interface for Windows would not be seen for a while longer. Other features such as device-independent resolutions, rasterized icons, virtual folders, and registry virtualization were discussed as well.
Build 5048's closer resemblance to Windows XP than to the prior Longhorn builds from 2003 surprised many, leading well-known Windows enthusiast Paul Thurrott to write: "My thoughts are not positive, not positive at all. This is a painful build to have to deal with after a year of waiting, a step back in some ways. I hope Microsoft has surprises up their sleeves. This has the makings of a train wreck."[12] Months later, Thurrott stated that the Vista development process has since recovered in the more recent builds.
Mid-2005 to present: Windows Vista
Beta 1
Windows Vista Beta 1 (build 5112, build date of July 20, 2005) was released on July 27 2005, and was available to Microsoft Developer Network (MSDN) and TechNet subscribers as well as a select group of Microsoft Beta testers.
Compared with the WinHEC build released earlier in the year, Vista Beta 1 was a large advancement in introducing new user interface features. The Windows Shell was drastically changed yet again, introducing virtual folders, a new search interface, a number of new high-resolution icons, and a revamped Windows Explorer interface which did away with the menus and most of the toolbar buttons that were present in previous versions. Beta 1 also introduced many of the underlying technologies slated for Vista, including the new networking and audio stacks, parental controls, and fairly complete working build of .NET Framework 3.0, then still referred to as WinFX.
Community Technology Preview
Build 5219 (build date of August 30 2005), Microsoft started releasing regular Community Technical Previews (CTP) to beta testers, with less stability work made to them than actual betas. Build 5219, also known as CTP1 and September CTP, was distributed among 2005 PDC attendees on September 13 2005, and has been released to Microsoft Beta testers and MSDN subscribers. This was the first public "Ultimate Edition" build, including Smart Fetch. Although not enabled by default, this refresh sees the return of the Windows Sidebar, which had been removed as part of the development reset, and the introduction of Desktop Gadgets, both of which are part of Microsoft gadgets line of mini-applications, which are similar to Yahoo Widget Engine's widgets. Microsoft has stated that these Gadgets will be available for download at www.microsoftgadgets.com, and they will be available for Windows XP as well. This build also supported a new version of Windows Media Center code-named "Diamond" (previously available only in Windows XP Media Center Edition). Although Microsoft has stated that WinFS will not make its wide-reaching debut in Windows Vista, users of the 5219 build noticed that WinFS is in fact included in that version. Several Windows 'rumor' sites and newsgroups such as Neowin and Paul Thurrott's Windows SuperSite have made speculation that WinFS will in fact be ready on time for Windows Vista's release, but this turned out to be untrue when Microsoft cancelled WinFS in June of 2006.
Build 5231 (build date of October 4 2005), also known as CTP2 or the October 2005 CTP, to MSDN subscribers and Microsoft Beta Testers on October 17 2005. This "Ultimate" build had more stability than the previous leaked build and introduced Windows Media Player version 11[13].
Windows Vista TAP Preview (built on November 17 2005 with a build number of 5259) was released to TAP members, four days after its originally announced release date of November 18 as a November CTP. Microsoft cancelled the November CTP due to its instability, and decided to release it only to TAP members. Sidebar was temporarily removed; the build had a few new UI changes, including the ability to change the color and clarity of the UI. Windows AntiSpyware (soon to be "Windows Defender") was integrated. Also, this build featured an updated version of Windows Mail. It is an IDW build and therefore had not gone through the CTP testing process.
Build 5268 (built date of December 5 2005 was released to some of Microsoft's OEM partners. In this build, Windows AntiSpyware was renamed Windows Defender, and IE7 had a new icon/logo. There were some minor UI changes.
December CTP (built on December 14 2005 with a build number of 5270), was released to testers and MSDN on December 19 and shared many similarities to build 5268, was very close to feature-complete. Since then, the feature complete build was delayed until late January, 2006.[14]
Build 5276 (built on December 23 2005) was released internally and previewed at CES 2006.
February CTP (built on February 17 2006 with a build number of 5308), released on February 22 2006 was the first feature-complete CTP. This build was meant for enterprises. It was also the first build to have the upgrade compatibility. This build, according to Microsoft, has all but one feature (which should appear in the next CTP) that customers will see in the final release. Vista is still in the stage of development so the final build may have more improvements than previously expected. An unstaged revision was made to this build and was released on February 28 2006 as build 5308.60 (built on February 23), which was released as a result of Windows Server "Longhorn" having many issues. There are supposedly no changes to Windows Vista since build 5308.17, but some people claim that this build is "faster, smoother, and without memory leaks".
February CTP Refresh (built on March 21 2006 with a build number of 5342) was released March 24 2006. This build was shipped to technical beta testers and some corporate customers by Microsoft and was being used as a testing board for the extensive feedback they've gotten since the February CTP. They described this release as an "External Developer Workstation", with the intent of providing an interim build between CTPs. Microsoft claimed it was still on track to deliver the next CTP in the second quarter, the build that will be the last in the Beta 2 fork. This build includes minor UI changes, most notably improvements to the Media Center, new Aero and Aurora effects, a faster setup process, some new Sidebar gadgets, and slight improvements in overall performance and stability. Paint was also slightly improved, there's a new screenshot snapping/saving tool included, and a slightly redesigned Network Center. This build did not meet CTP quality measurements, and was available only in Ultimate Edition, for both 32-bit (x86) and 64-bit (x64) systems.
April EDW (built on April 19 2006 with a build number of 5365), which was released on April 21 2006, introduced more changes to visual user interface elements, and to the behavior of User Account Control. A number of new backgrounds were also introduced, and two new screensavers were added as well. The Sidebar was enabled by default, as was automatic defragmentation of the hard drive. Texas Hold'em, a game that shipped with some previous CTPs, was dropped due to apparent "political sensitivity" issues; Microsoft is planning on offering it as a separate web download after Vista's release.
Windows Vista Beta 2 Preview (built on May 1 2006 with a build number of 5381) was released on May 6, 2006 to Microsoft's technical beta testers. It featured mostly performance tweaks and only a few minor changes compared to build 5365. With this build, Microsoft entered Beta 2 "escrow".
Beta 2
Windows Vista Beta 2 (built on May 18 2006 with a build number of 5384), was released to Microsoft Developer Network subscribers (the first since 5308) and Microsoft Connect testers on May 23 2006 in conjunction with Bill Gates's keynote presentation at the WinHEC 2006 conference. On June 6, Microsoft extended the availability of Beta 2 to all users, making Vista available as a free download in several languages from their web site. Some technology web sites have described this release as "the largest download event in software history".[15]
On June 14 2006, Windows developer Philip Su posted a blog entry which decried the development process of Windows Vista, stating that "the code is way too complicated, and that the pace of coding has been tremendously slowed down by overbearing process. "[16] The same post also described Windows Vista as having approximately 50 million lines of code, with about 2,000 developers working on the product.
Pre-RC1
Build 5456 (build date of June 20 2006) was released on June 24, 2006. Some of the new features include a revamped Aero subsystem, and a completely overhauled and significantly less obtrusive User Account Control interface. "List view" in Windows Explorer has been restored, after having disappeared in recent builds. The release notes for the build state that the Time Zone bug that plagued almost all previous builds of Windows Vista has been patched, and quite a few issues in the Regional Settings and IME have also been resolved. A new "Windows Aero" mouse pointer scheme was introduced, with anti-aliasing being introduced to the mouse pointer for the first time, and many of the remaining Windows XP-style icons have been replaced with new icons. The disk space used by a new installation has also been significantly reduced.
Build 5472 (build date of July 13 2006) was released on July 17 2006.[17] Aside from incorporating a number of bug fixes and localization improvements, this build also introduces a revised "Basic" theme that replaces the gray theme seen in previous builds with a light blue theme. The Network Center was significantly revised as well, collating more status information in one place, and reducing the number of steps to get to most configuration options. More desktop backgrounds and icons have been introduced, and Flip3D saw some layout tweaks. This build has a huge performance improvement over Beta 2 and is comparable to and possibly even faster than that of Windows XP.[18][19]
Build 5483 (build date of July 21, 2006), Build 5487 (August 2, 2006), Build 5492 (August 10, 2006), Build 5505 (August 13, 2006), and Build 5520 (August 17, 2006) were made available to a limited number of TAP testers. These builds feature a revised window of customizing the color and appearance of Windows Aero, new sidebar gadgets including a weather gadget and a calendar, improvements to anti-aliasing in Flip3D, and other interface changes. Although the desktop is badged as RC1, these builds were still Pre-RC1 builds (the desktop in Build 5520 is tagged Pre-RC1).
During a demonstration of the speech recognition feature new to Windows Vista at Microsoft's Financial Analyst Meeting on July 27 2006, the software recognized the phrase "Dear mom" as "Dear aunt". After several failed attempts to correct the error, the sentence eventually became "Dear aunt, let's set so double the killer delete select all".[20][21] A developer with Vista's speech recognition team later explained that there was a bug with the build of Vista that was causing the microphone gain level to be set very high, resulting in the audio being received by the speech recognition software to be "incredibly distorted".[22]
Build 5700 (build date of August 10, 2006) was shown at the Student Day Presentation of Microsoft Tech-Ed 2006 in Australia. It appeared to run faster than Build 5472 with few UI improvements.[23]
Build 5536 (build date of August 21, 2006) was released on August 24, 2006 to members of the Technet beta program[24]. Among notable changes, it featured new ties to the Windows Live online services by new icons in the Welcome Center, minor updates to the Aero appearance with a slightly more bluish tint to the glass effect, and further tweaked anti-aliasing in the Flip 3D feature. It was released publicly on August 29 2006 [1]
Microsoft expects to release Windows Vista RC1 to the public on or after September 7, 2006[25] via the Customer Preview Program.
See also
- Windows Vista
- Features new to Windows Vista
- Copland and Mac OS 8 — a historical example of an ambitious software project forced to abort development and retool mid-cycle, and its result
References
- ^ Peter Galli (July 30 2001). "Pushing Forward - the next version of Windows". eWeek. Retrieved 2006-07-07.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ http://www.winsupersite.com/images/reviews/lh_alpha_029.gif
- ^ Thurrott, Paul (2002-11-13). ""Longhorn" Alpha Preview". Windows SuperSite. Retrieved 2006-03-30.
{{cite web}}: CS1 maint: year (link) - ^ Thurrott, Paul (2003-03-01). "Longhorn Alpha Preview 2: Build 4008". Windows SuperSite. Retrieved 2006-03-30.
{{cite web}}: CS1 maint: year (link) - ^ "WinHEC 2003 Session Presentations". Microsoft. 2003-08-01. Retrieved 2006-03-31.
{{cite web}}: CS1 maint: year (link) - ^ Thurrott, Paul. "WinInfo Short Takes: Week of September 29". SuperSite for Windows. Retrieved 2006-03-31.
- ^ Kaplan, Michael (2005-10-16). "A reset does not mean everything was thrown away". Sorting It All Out. Retrieved 2006-04-02.
{{cite web}}: Check date values in:|date=(help) - ^ Guth, Robert (2005-09-23). "Battling Google, Microsoft Changes How It Builds Software". The Wall Street Journal. pp. A1, ??.
{{cite news}}: Check date values in:|date=(help) (viewable online here) - ^ Thurott, Paul (2003-04-16). "Brian Valentine talks Windows Server 2003". SuperSite for Windows. Retrieved 2006-04-02.
{{cite web}}: Check date values in:|date=(help) - ^ Murphy, Victoria (2003-05-26). "The Exterminator". Forbes Magazine.
{{cite web}}: Check date values in:|date=(help) - ^ "Rob Short (and kernel team) - Going deep inside Windows Vista's kernel architecture". Channel 9. Microsoft. 2005-12-23.
{{cite web}}: Check date values in:|date=(help); Unknown parameter|coauthors=ignored (|author=suggested) (help) - ^ Thurrott, Paul (2005-04-26). "WinHEC 2005: Day Two Blog". SuperSite for Windows. Retrieved 2006-04-02.
{{cite web}}: Check date values in:|date=(help) - ^ http://www.microsoft.com/presspass/newsroom/winxp/WinVistaCTPFS.mspx
- ^ http://www.microsoft.com/presspass/newsroom/winxp/12-19WinVistaDecCTPFS.mspx
- ^ Matt Mondok (June 10 2006). "Windows Vista Beta 2: largest download event in software history". Microsoft.ars Journal. Ars Technica. Retrieved 2006-06-11.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ "Broken Windows Theory". The World As Best As I Remember It. MSDN Blogs. June 14 2006. Retrieved 2006-06-24.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ Nick White (July 18 2006). "Windows Vista Build Number 5472". Windows Vista Team Blog. TechNet Blogs. Retrieved 2006-07-28.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ http://bink.nu/Article7770.bink
- ^ http://bink.nu/Article7771.bink
- ^ "Glitch in voice-recognition software foils Microsoft demo". Associate Press. The City Herald. July 28 2006. Retrieved 2006-07-30.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ Video footage.
- ^ Rob Chambers (July 29 2006). "FAM: Vista SR Demo failure -- And now you know the rest of the story ..." Rob's Rhapsody. MSDN Blogs. Retrieved 2006-07-31.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ Zheng, Long (2006-08-22). "TechEd Day 1 - Student Day". istartedsomething. Retrieved 2006-08-23.
{{cite news}}: Check date values in:|date=(help) - ^ Ina Fried (August 25 2006). "Windows Vista inches forward". CNET News.com. Retrieved 2006-08-27.
{{cite web}}: Check date values in:|year=(help)CS1 maint: year (link) - ^ Thurott, Paul (2006-08-15). "Exclusive: Microsoft Still Plans October 2006 Vista Release". Windows IT Pro. Retrieved 2006-08-19.
{{cite news}}: Check date values in:|date=(help)
External links
- Windows Vista Bug Reports: An Analysis – Robert McLaws' analysis of bug counts through the Windows Vista beta test period