Discussion in 'Windows Desktop Systems' started by NetRyder, Jul 9, 2005.
Dude I'm jealous, how do I sign up?
Ready to go, also signed an NDA today which means I can't talk about longhorn for 5 years, unless the information becomes available elsewhere lawfully first...
I tried signing up for that stuff and never got a confirmation email from them ..
Seems like these invites (perhaps the first set?) were only sent out to WinHEC attendees then? And people who asked attendees to sign up for them at the booth... *cough*
No worries though.
1) Beta 1 will probably leak...heh.
2) Beta 2 will be more interesting from an end-user standpoint, and as a result, might be more widely available.
I'll have to sign one of those sometime soon too, as part of the MSA program...
We are talking about a special forum, on another site beginning with ne, where we will be able to provide feedback on longhorn etc, if we don't like newsgroups. I don't like newsgroups at all!
Hmm, I wonder what forum that would be
I'm always left out
After working with some beta stuff?
I'll get this another way
Oh, so this section you're talking about will be restricted to people in the technical beta only then? Is it officially supported by Microsoft?
Sounds cool. I'm not a fan of newsgroups either.
Yeah, it all depends on MS permission.
Well it's rather expensive, expecially if one can't get it education discounted. But MSDN subscribers get the stuff shipped to them by release candidate status at least. They didn't ship an NDA with the shipment of CDs either...
Though winXP did come beta 1, most things don't, so the subscribers wouldn't typically get it so soon...
At least I'm not the only one! :cry:
God, I never get sick of your posts. You have the HOTTEST Avatar!
Thurrott's now reporting that Beta 1 is scheduled for release on July 27th. Let's see...
I read Thurrott's report on Longhorn. I do have a question. Why does MS fork beta builds? Why have bug-filled builds running, when everyone should concentrate on making one build bug-free?
Short answer - because it would take forever to get future builds out.
Long answer - Since Beta 1 is being sent out for external testing, the sole emphasis in that branch is to check in fixes for any bugs that are marked as beta1-blockers. Think of it as a feature-frozen build where no feature additions are being made.
Meanwhile, development has to continue if the team has to meet future deadlines (such as the PDC build in September, Beta 2, and so on). The Beta 2 trunk is where any new features are being checked in. Following such a system makes sure that no new bugs are introduced into the builds leading up to Beta 1 as a result of feature additions.
Got it, Bud.
Thanks for the explanation.