Recommended Posts

According to sources at Microsoft, the software giant has set its new sights on August 10th as the release date for Longhorn Beta 1, although that date obviously could slip if the company is unable to hit internal bug requirements yet again. The current escrow build for Longhorn Beta 1 is 5113, a few builds older than build 5103, the current internal build in the beta 1 fork.

Microsoft recently forked the Longhorn build process to segregate the beta 1 code check-ins from the post-beta 1 (or what we can think of as the beta 2) code path. Recent leaks of Longhorn builds are from the beta 2 code path, but we can expect them to be quickly eclipsed by the beta 1 code base as Microsoft makes that milestone widely available.

As far as the beta 1 schedule is concerned, Microsoft's test teams are required to complete testing by July 28 but they need to achieve the "0 active bug" designation to ship beta 1. Yesterday, the beta 1 fork still had 123 active bugs. That number had dropped to 86 by today.

This slip was to be expected but it will be shipping to Software developers tonight or tomorrow morning....

According to sources at Microsoft, the software giant has set its new sights on August 10th as the release date for Longhorn Beta 1, although that date obviously could slip if the company is unable to hit internal bug requirements yet again. The current escrow build for Longhorn Beta 1 is 5113, a few builds older than build 5103, the current internal build in the beta 1 fork.

 

Microsoft recently forked the Longhorn build process to segregate the beta 1 code check-ins from the post-beta 1 (or what we can think of as the beta 2) code path. Recent leaks of Longhorn builds are from the beta 2 code path, but we can expect them to be quickly eclipsed by the beta 1 code base as Microsoft makes that milestone widely available.

 

As far as the beta 1 schedule is concerned, Microsoft's test teams are required to complete testing by July 28 but they need to achieve the "0 active bug" designation to ship beta 1. Yesterday, the beta 1 fork still had 123 active bugs. That number had dropped to 86 by today.

This slip was to be expected but it will be shipping to Software developers tonight or tomorrow morning....

586280475[/snapback]

Where is this from?

According to sources at Microsoft, the software giant has set its new sights on August 10th as the release date for Longhorn Beta 1, although that date obviously could slip if the company is unable to hit internal bug requirements yet again. The current escrow build for Longhorn Beta 1 is 5113, a few builds older than build 5103, the current internal build in the beta 1 fork.

 

Microsoft recently forked the Longhorn build process to segregate the beta 1 code check-ins from the post-beta 1 (or what we can think of as the beta 2) code path. Recent leaks of Longhorn builds are from the beta 2 code path, but we can expect them to be quickly eclipsed by the beta 1 code base as Microsoft makes that milestone widely available.

 

As far as the beta 1 schedule is concerned, Microsoft's test teams are required to complete testing by July 28 but they need to achieve the "0 active bug" designation to ship beta 1. Yesterday, the beta 1 fork still had 123 active bugs. That number had dropped to 86 by today.

This slip was to be expected but it will be shipping to Software developers tonight or tomorrow morning....

586280475[/snapback]

Sorry, I disagree. My sources say this:

Meanwhile, the Beta 1 team just needs to get the bugs to zero. Basically, there are 3 kinds of bugs -- red, yellow, and green. Red bugs are the critical ones that have to get to zero before they can release it. Yellow bugs are not critical and not required for release, although they would like to get that as low as possible, especially if there is time after red goes to zero. If they are not done, they simply go to the Beta 2 track. Green bugs are essentially ignored for this release unless there is time to fix them, especially if red goes to zero and yellow goes to zero.

The numbers change every day. Red did go to zero by Friday the 22nd, which was the goal. Therefore, release can proceed.

According to sources at Microsoft, the software giant has set its new sights on August 10th as the release date for Longhorn Beta 1, although that date obviously could slip if the company is unable to hit internal bug requirements yet again. The current escrow build for Longhorn Beta 1 is 5113, a few builds older than build 5103, the current internal build in the beta 1 fork.

 

Microsoft recently forked the Longhorn build process to segregate the beta 1 code check-ins from the post-beta 1 (or what we can think of as the beta 2) code path. Recent leaks of Longhorn builds are from the beta 2 code path, but we can expect them to be quickly eclipsed by the beta 1 code base as Microsoft makes that milestone widely available.

 

As far as the beta 1 schedule is concerned, Microsoft's test teams are required to complete testing by July 28 but they need to achieve the "0 active bug" designation to ship beta 1. Yesterday, the beta 1 fork still had 123 active bugs. That number had dropped to 86 by today.

This slip was to be expected but it will be shipping to Software developers tonight or tomorrow morning....

586280475[/snapback]

That is old news, I read that somewhere else last week. You need to post sources and dates if you copy and paste as well.

Sorry, I disagree.  My sources say this:

Meanwhile, the Beta 1 team just needs to get the bugs to zero. Basically, there are 3 kinds of bugs -- red, yellow, and green. Red bugs are the critical ones that have to get to zero before they can release it. Yellow bugs are not critical and not required for release, although they would like to get that as low as possible, especially if there is time after red goes to zero. If they are not done, they simply go to the Beta 2 track. Green bugs are essentially ignored for this release unless there is time to fix them, especially if red goes to zero and yellow goes to zero.

The numbers change every day. Red did go to zero by Friday the 22nd, which was the goal. Therefore, release can proceed.

586280485[/snapback]

I agree with Pro, I heard from a MS source as of yesterday that today between 3pm-4pm PST was the goal for availability.

Sorry, I disagree.  My sources say this:

Meanwhile, the Beta 1 team just needs to get the bugs to zero. Basically, there are 3 kinds of bugs -- red, yellow, and green. Red bugs are the critical ones that have to get to zero before they can release it. Yellow bugs are not critical and not required for release, although they would like to get that as low as possible, especially if there is time after red goes to zero. If they are not done, they simply go to the Beta 2 track. Green bugs are essentially ignored for this release unless there is time to fix them, especially if red goes to zero and yellow goes to zero.

The numbers change every day. Red did go to zero by Friday the 22nd, which was the goal. Therefore, release can proceed.

586280485[/snapback]

yea my post is a fake i was just stiring the pot, trying to livin the party up..because if that were to happen alot of hearts would be crushed on this day 27th july 2005.

yea my post is a fake i was just stiring the pot, trying to livin the party up..because if that were to happen alot of hearts would be crushed on this day 27th july 2005.

586280498[/snapback]

Like any of us need that crap. Neowinians are already about ready to raid Redmond.

According to sources at Microsoft, the software giant has set its new sights on August 10th as the release date for Longhorn Beta 1, although that date obviously could slip if the company is unable to hit internal bug requirements yet again. The current escrow build for Longhorn Beta 1 is 5113, a few builds older than build 5103, the current internal build in the beta 1 fork.

 

Microsoft recently forked the Longhorn build process to segregate the beta 1 code check-ins from the post-beta 1 (or what we can think of as the beta 2) code path. Recent leaks of Longhorn builds are from the beta 2 code path, but we can expect them to be quickly eclipsed by the beta 1 code base as Microsoft makes that milestone widely available.

 

As far as the beta 1 schedule is concerned, Microsoft's test teams are required to complete testing by July 28 but they need to achieve the "0 active bug" designation to ship beta 1. Yesterday, the beta 1 fork still had 123 active bugs. That number had dropped to 86 by today.

This slip was to be expected but it will be shipping to Software developers tonight or tomorrow morning....

586280475[/snapback]

that's ancient news. i think paul thurott mentioned that maybe 1-2 weeks ago.

Chris Jones, VP who runs the build team for Windows Vista, among others, was great yesterday (we interviewed him for Channel 9). Anyway, we're trying to get that video up this afternoon sometime. On campus there's a big party thanks to shipping Beta 1. He said they would sign off on the beta at a meeting this morning and that it would be on MSDN Universal soon.

So, MSDN subscribers should get it today and not Aug. 3 :huh:

15mins?

586280519[/snapback]

Microsoft to release Windows version

By Brier Dudley

Seattle Times technology reporter

The worst-kept secret in Redmond is the release date for a nearly completed

version of Windows Vista.

A "beta" test version of the company's new operating system, formerly known

by the code name Longhorn, is being released to software developers for

testing this morning. That's a few days earlier than a deadline Microsoft

gave when it released the product name last week.

Details of the long-awaited release were widely reported yesterday by

software-enthusiast sites, but spokespersons insisted those reports were

only rumors and speculation. They wanted the news held until today, which

would have put it in newspapers tomorrow, the day of the company's annual

financial-analysts meeting.

Microsoft has been trickling out previews of the software since October

2003, but today's beta is a milestone in the development process. It's a

polished version that can be run and tested by programmers and computer

makers as they start building Vista-based products to go on sale along with

Vista in late 2006.

More than a third of Microsoft's employees in Redmond have worked directly

or indirectly on the product, which is likely to run most of the world's

computers in the coming decade. It's also the first PC operating system to

be released since Microsoft made security and reliability top priorities.

New features planned for Vista that have been already reported or disclosed

by the company include:

. A built-in desktop search tool that appears just above the Start button.

It lets users quickly find all sorts of files stored on the PC; results are

displayed as thumbnail images of the documents that are found.

. A new version of Internet Explorer with built-in tools to prevent

"phishing" scams that fool users into thinking they're at a secure Web site.

The browser will also be available for users of Windows XP.

. New operating modes that make it easier for users to log in and use their

PCs without administrative-level control of the system. Most consumers use

their PCs today in an administrative mode that makes them more vulnerable to

attack; new modes could make it easier for companies to manage PCs.

. A new translucent desktop appearance and improved display and

communication capabilities.

Microsoft has also been working with computer hardware developers on ways to

make Vista-based machines power up faster.

The timing of the release was widely reported online yesterday despite the

efforts of Microsoft's public-relations firm to manage the news. Aside from

the analysts meeting, Microsoft is always wary of specifying timing because

of the potential for last-minute delays.

Reporters were briefed on the release details yesterday on condition the

news be held until after the software is released on Microsoft's developer

Web site this morning.

"It seems like sort of an odd sequence of events for me; it seems to be

maybe timed to the analyst conference Thursday," said Dwight Davis, a

Kirkland-based industry analyst at Summit Strategies, who was briefed on the

release plans yesterday. "I can't imagine that too many of the financial

analysts who are attending will want to rush right home with their beta code

and start playing with it."

Davis said the beta version is incomplete, but has many "gee whiz" features

that will interest people. Businesses will be particularly interested in the

administrative features.

Although today's beta release is ahead of the Aug. 3 deadline Microsoft gave

last week, it's a stretch to say the product is ahead of schedule.

Executives said in the past that 2005 was a target for delivering the final

version.

The company will also be under pressure to get all the new features sorted

out in time for a late 2006 release, said Michael Cherry, a former Microsoft

engineer now at the Directions on Microsoft research company in Kirkland.

Brier Dudley: 206-515-5687 or [email protected]

Copyright ? 2005 The Seattle Times Company

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I recently tried edge. It seems a lot better. A lot of the junk in it is gone. It seems less bloated and snappy.
    • Lethal fake phone chargers are still being sold on Amazon and eBay, UK watchdog warns by Paul Hill Credit: Pexels The UK consumer rights organization, Which?, is claiming that “potentially lethal knock-off chargers” are still being sold on online marketplaces seven years after it exposed the danger of these chargers. In its latest investigation, it bought 15 USB phone chargers from several online marketplaces and found they were missing key information, meaning they cannot be legally sold in the UK. Which? bought the 15 chargers from seven online marketplaces. These were Amazon (including Amazon Haul), AliExpress, B&Q Marketplace, Debenhams Marketplace, and eBay. It said that the chargers were so badly made that anyone using them was at risk of electric shock. Over half the chargers also posed fire and explosion risks. Of the chargers purchased, one was a fake Apple USB-C 35W power adaptor charger. To confuse buyers, the box was branded with an Apple logo, but testing found it to be a fake. Further testing picked up arcing sounds after 10 seconds of use, where a current jumps between two parts of the electrical circuit, which can cause fires, explosions, or electric shock. The manufacturers of this particular charger also put modeling clay inside it to make it feel more weighty, robust, and genuine. Not all of the chargers were technically faulty; however, some were missing key packaging, markings, and documentation, meaning they can’t be sold in the UK legally. Which? said that it is now campaigning alongside a coalition of safety groups and businesses for new laws that make online marketplaces responsible for ensuring the safety of products that they choose to list on their websites. It also said the government needs to start using powers under the Product Regulation and Metrology Act, which was adopted last July, to impose safety requirements on online marketplaces via secondary legislation, but so far, there have been delays. No matter what country you are in, be sure to properly research what you are buying and only buy authentic chargers to prevent fires. You can read more about Which?’s research here.
    • Visual Studio finally gets long-awaited feature that developers will love by Usama Jawad Visual Studio Code is Microsoft's popular, lightweight, open-source code editor, it is actually Visual Studio that is the company's flagship integrated development environment (IDE). Although the IDE already offers a boatload of useful features for developers, Microsoft has finally introduced a long-requested capability that will be loved by many. While developers have already been able to create Git pull requests (PRs) directly within Visual Studio for the past couple of years, it had not been possible to review a PR without switching to the browser, until now. Microsoft revealed in December 2025 that it is working on UX that enables developers to do just that, and fast-forward to June 2026, and Visual Studio finally has native capabilities to open and inspect a PR, discuss feedback, and wrap up the review, all without switching to the browser. This integration works for both GitHub and Azure DevOps (including on-prem). Developers have access to multiple surfaces to open a PR, including Git Repository, Git Changes, and the Git menu in Visual Studio. Once you open a PR, all the important details will be immediately visible to you, from where you can navigate to various levels of granularity and branch states, depending on the reviews that you are engaged in. As you would expect, you also get a diff view that enables you to see code changes inline or side-by-side in a separate panel. You can also review commit-by-commit. Additionally, this UX fosters collaboration as you can leave comments, reply to threads, and resolve conversations easily. Naturally, you can also leverage Copilot to apply a code suggestion to fix a potential issue. When you are done, you have the ability to approve, complete, and merge the PR. This is a pretty major feature as it has been requested heavily for the past few years. You can try it out in Visual Studio 2026 version 18.7, made available here recently. Microsoft plans to enhance this experience further in future releases with comment filtering, a timeline of PR activity, and more.
    • This AdGuard Family lifetime deal is still only $15.97 by Steven Parker Today's highlighted Neowin Deal comes via our Apps + Software section, where you can get a lifetime subscription and save 90% on a lifetime AdGuard Family Plan. AdGuard is a unique program that has all the necessary features for what they claim to be "the best web experience." The software combines the an advanced ad blocker, a privacy protection module, and a parental control tool—all working in one app. This software deals with annoying ads, hides your data from a multitude of trackers, protects you from malware attacks, and even lets you restrict your kids from accessing inappropriate content. Install AdGuard and see the internet as it was supposed to be: clean and safe. Get rid of annoying banners, pop-ups & video ads once and for all Hide your data from the multitude of trackers & activity analyzers that swarm the web Avoid fraudulent and phishing website and malware attacks Protect your kids online by restricting them from accessing inappropriate & adult content Good to know Family Plan Length of access: lifetime This plan is only available to new users Redemption deadline: redeem your code within 30 days of purchase Max number of devices: 9 Access options: desktop & mobile Software version: AdGuard Family Updates included A lifetime subscription of AdGuard Family Plan normally costs $169.99, but this deal can be yours for just $15.97, that's a saving of $157.02. For full terms, specifications, and license info please click the link below. Get this AdGuard Family lifetime deal for just $15.97 (was $169.99) Although priced in U.S. dollars, this deal is available for digital purchase worldwide. As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support! Support queries If you have queries or need support for any of the Neowin Deals, please use the contact form here. Neowin Deals are managed and sold by StackCommerce who represent Neowin on an affiliate basis. Why we post these deals We post these because we earn commission on each sale so as not to rely solely on advertising, which many of our readers block. It all helps toward paying staff reporters, servers and hosting costs. So for those that keep moaning and complaining, be thankful we're still online for you to even do that. Other ways to support Neowin Whitelist Neowin by not blocking our ads Create a free member account to see fewer ads Make a donation to support our day to day running costs Subscribe to Neowin - for $14 a year, or $28 a year for an ad-free experience Disclosure: Neowin benefits from revenue of each sale made through our branded deals site powered by StackCommerce.
    • the MCT currently downloads 26200.8653, so not completely up to date.
  • Recent Achievements

    • Week One Done
      Timaximus earned a badge
      Week One Done
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Rookie
      FBSPL went up a rank
      Rookie
    • First Post
      davidbazooked earned a badge
      First Post
    • Week One Done
      davidbazooked earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!