Windows Vista Beta 1

[Sammyinnit]

Amen to that :laugh:

586280429[/snapback]

Agreed, LOL.

[P!P]

and you believe that?

586280425[/snapback]

I have this friend who said he knows god and that God said Vista will be released in 3 hours and have build number AB56. ;)

[JCDerrick]

If I was a betting man...

I'd say 5113-5115.

Some speculate it'll stay 5112 (same as Longhorn Lab), but I don't think so. I think they'll change it a numeral or two.

[Coffeee]

I have this friend who said he knows god and that God said Vista will be released in 3 hours and have build number AB56.  ;)

586280439[/snapback]

I heard that one too... Do you know Richard (Dick) Edd aswell do you? :shifty:

[Sammyinnit]

I heard that one too... Do you know Richard (Dick) Edd aswell do you? :shifty:

586280449[/snapback]

:rofl: This thread gets funnyer.

[Coffeee]

:rofl: This thread gets funnyer.

586280456[/snapback]

Well I do try to keep my fellow neowinians happy :whistle:

[mikebeech]

hey, does anyone know if the wireless will work in this beta? as there was not much support for it in the previous builds :(, would be cool if it did :D

[RightfulSpire]

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....

[jphillips59]

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?

[JCDerrick]

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.

[ev0|]

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.

[jphillips59]

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.

[P!P]

The Beta 1 source has been locked since May. How can they not be ready? Also, why would they work so hard to get zero bugs for Beta 1. Is that what a beta and beta testers are for?

[RightfulSpire]

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.

[farangcm]

They keep a record of their testes to make sure they are not just on the program.

586279696[/snapback]

I wouldn't put it past them! :cool:

Allen

[P!P]

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.

[DOCa Cola]

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]

:sleep:

[BigGiantHead]

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.

[mad_onion]

:rolleyes: :no: well please dont do it because its very strange and annoying.

[beauvoir]

15mins?

[Hurmoth]

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:

[tra]

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

[Poof]

The wait is unbearable...

I WANT IT NOW!!! =)

[duba-antivirus]

so doooooooooooo i !

[minkcar]

im about to cry, hurry up ms !