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

    • Sadly, that is the state of things. It's basically considered acceptable for any random app running on your computer to use 1+ GB of RAM, and install space, lol, no one even seems to consider that.
    • EU Commission explains why Siri AI isn't launching in the EU, and Apple is to blame by Hamid Ganji Image via Apple This week at Apple’s 2026 developers conference, the iPhone maker unveiled the upgraded Siri after more than a year of delays. The new Siri is now called Siri AI, and it's powered by Google Gemini models. While Siri AI is preparing to roll out to Apple users worldwide, the company’s EU customers might need to wait much longer before getting their hands on the new assistant. Shortly after announcing iOS 27, Apple said in a blog post that Siri AI is not coming to the EU anytime soon due to hurdles posed by the Digital Markets Act (DMA) and other regulatory requirements. To comply with the DMA in the EU, Apple apparently needs to open Siri AI to rival assistants on iOS 27 and iPadOS 27. Apple has refused to do so, which has resulted in Siri AI being delayed for its EU users. The company argues that such a move would put users’ privacy at risk. In a statement to Neowin, a European Commission spokesperson provided more details about why Siri AI will not be rolled out to Apple customers in the region. The statement first noted that the DMA does not prohibit Apple from launching its services in the EU and that the company is simply required to comply with the law. The European Commission spokesperson added that, since Apple is considered a gatekeeper under the DMA, it is “obliged to give third parties access to equivalent features as they give to its own products. Because the DMA is precisely about giving users the choice to use the product they find best suits their needs.” Moreover, the spokesperson said the Commission has been in contact with Apple, though the company “did not develop proposals for DMA compliant interoperability solutions.” The statement also clarified that companies designated as gatekeepers cannot leverage their status and products, such as operating systems, to favor their own AI services. The first public beta of iOS 27 will roll out next month, while the stable version is expected to launch this fall following the release of the iPhone 18 series. It remains unclear when Apple will be able to resolve its DMA-related compliance issues with the European Commission and bring Siri AI to its European customers.
    • i wish i could uninstall Chrome from Anrdoid...  
    • XMedia Recode 3.6.3.1 by Razvan Serea XMedia Recode is a free video and audio converter. XMedia Recode supports nearly all audio and video codecs. With XMedia Recode you can easily convert nearly all film and music files in the format you want. Convert for countless devices, select the predefined profile (iPhone, iPad, iPod Touch, Android-Tablets, Sony PSP, Amazon Kindle, Smartphones Blackberry, Wii und DS, Cowon, Android, HTC, Xbox360, Samsung, LG). XMedia Recode converts: 3GP in AVI, 3GP in FLV, AC3 in MP3, AC3 in WAV, ASF in 3GP, ASF in FLV, ASF in MP4, AVI in FLV, AVI in 3GP, FLAC in MP3, FLAC in WMA, FLV in 3GP, FLV in Mp3, DVD in 3GP, DVD in AC3, DVD in AVI, DVD in MP3, DVD in MP4, DVD in MOV, DVD in SVCD, DVD in VCD, DVD in WMV, OGG in MP3, OGG in WMA, MPEG in AVI, MP2 in MP3, MP4 in FLV, MP4 in AVI, M4P in MP3, MOV in 3GP, MOV in AVI, MOV in FLV, WMA in MP3, WMV in FLV, WAV in MP3. Main functions of XMedia Recode: Extracts audio tracks from DVD, Blu-ray and video files Framework also freely selectable color (Padding) Drag-n-drop of video files directly on the encoder Selection display format (1: 1, 3:2, 4:3, 5:4, 5:6, 11:9,16: 9, 16:10, 2.21: 1) Zoom shot (none, type character box, media, Pan Scan, to screen) ''Direct Stream'' copies the audio stream or video stream into the target format 2-Pass-Encoding Volume correction Can change framerate, bit rate, resolution Can extract audio stream of most video formats Produce DVD copies for mobile phones, various mobile devices Edit Video: Color correction Video cut Cropping Denoise Delogo Deblocking De-interlacing Flip Image Start Time End Time Resolution Rotate Image Sepia Sharpness Padding Video fade in / fade out XMedia Recode 3.6.3.1 changelog: Update of ffmpeg Updated AOM AV1 Codec (3.14.1) Fixed minor bugs Download: XMedia Recode 64-bit | Portable ~20.0 MB (Freeware) Download: XMedia Recode 32-bit | Portable View: XMedia Recode Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This has been on the roadmap for years, nothing really new here. This is one of the few areas where Microsoft is making Windows better. Universal print is a very good things and so far works as expected. The last step is ending the option for 3rd parties to add traditional custom drivers. It is somewhat of a hurdle, but it is for a long-term good. The downside is that printer manufactures are likely going to use this as an excuse to force users onto new printers. Considering this roadmap has been public for years, then printers sold during that time should be covered...but I'm sure they will have a different opinion.
  • Recent Achievements

    • One Month Later
      pinnclepd earned a badge
      One Month Later
    • First Post
      X-No-file earned a badge
      First Post
    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      213
    3. 3
      +Edouard
      145
    4. 4
      Steven P.
      86
    5. 5
      ATLien_0
      83
  • Tell a friend

    Love Neowin? Tell a friend!