Microsoft Hits Windows Vista Beta 2 Delays


Recommended Posts

Sources at the company told me this week that Microsoft will soon delay the release of Windows Vista Beta 2 from December 7, 2005 to sometime in January or February 2006. However, because the Vista development schedule is extremely time constrained, the company will try and make up lost time by eliminating one of the planned release candidate (RC) milestones that were planned for later in the process.

A Microsoft representative told me that the company remains on track for shipping Windows Vista in the second half of 2006. "We are on schedule and committed to shipping on time and ensuring a high-quality product," I was told. "Microsoft sets internal targets for the development team around milestones, but these are not commitments to specific dates. We do not comment on these internal milestones and we have not announced a specific timeframe for our next major Windows Vista milestone. "

"That said, customers have told us repeatedly they prefer more frequent code drops through our Community Technology Preview (CTP) program [which] provides a great avenue for real time feedback and testing from our customers--feedback we formerly received only through the beta process. You should expect Microsoft to continue their focus to deliver CTPs in the coming months given how successful this program has been."

Previously, sources had revealed to me that Microsoft would at least delay the release of Windows Vista Beta 2 until late December. This more recent delay suggests that the company is having a difficult time meeting its internal shipping criteria for Beta 2, which is considered a major milestone release and will be made widely available to testers and the public. It's not known at this time whether the delay will affect related product releases such as Internet Explorer (IE) 7.0 Beta 2 and Windows Media Player 11 Beta 1, both of which were also originally set for a December 7 public release.

Source: http://www.windowsitpro.com/windowspaulthu...rott_48408.html

I think Microsoft is doing this because things are going too fast ... I don't think they want a Windows ME disaster all over again ...

586794430[/snapback]

oh god.. nobody wants another ME disaster.. stocks will plumit.. and microsoft will need to pull a magic trick out there asses if they ever do that again. ME is probably the worst thing to happen to PC's LOL

oh god.. nobody wants another ME disaster.. stocks will plumit.. and microsoft will need to pull a magic trick out there asses if they ever do that again.  ME is probably the worst thing to happen to PC's LOL

586794700[/snapback]

:ninja: I beta tested that. It was the worst thing I have ever been involved in.

I am generally optimistic about Microsoft's operations. But if this is true, somebody needs a major asswhooping ! :ninja:

Normally I would've said its better to get delayed than ship with bugs, but they'd a plenty of time even after the reset! :huh:

The problem recently has been the addition of new features. Post Beta1 they started adding all kinda of stuff. This brought on more instability. The November CTP which I hear we are still going to get should be much better than the 5231 builds we currently have.

The problem recently has been the addition of new features.  Post Beta1 they started adding all kinda of stuff.  This brought on more instability.  The November CTP which I hear we are still going to get should be much better than the 5231 builds we currently have.

586794848[/snapback]

Lets hope so :p

:ninja:  I beta tested that. It was the worst thing I have ever been involved in.

586794710[/snapback]

What exactly is wrong with Windows ME, may I ask? I know I stand out like a sore thumb when saying this but Windows ME truly wasn't that bad. It had its' problems, but, hey, every Windows had its' own issues.

What exactly is wrong with Windows ME, may I ask? I know I stand out like a sore thumb when saying this but Windows ME truly wasn't that bad. It had its' problems, but, hey, every Windows had its' own issues.

586794975[/snapback]

For me stability and performance were the biggest problems.

In gratuity I received the full version, which I appreciated but stayed with Windows 98SE. That was a very good operating system for its time.

What exactly is wrong with Windows ME, may I ask? I know I stand out like a sore thumb when saying this but Windows ME truly wasn't that bad. It had its' problems, but, hey, every Windows had its' own issues.

586794975[/snapback]

Well, it has more issues than other MS OS's in my opinion It was an memory-hog if there ever was one. Sure, you could set it proberly up if you was an it-expert, but for home users it sucks big time. By far the WORST OS from Microsoft. Not to mention its vulnerability to hackers, if it wasn't set perfect up, i never got it to work on computer when i upgraded some of the hardware (SoundBlaster Live!, not some strange borderline equipment)

I say if they need the extra time to ship a proper Beta 2, then be my guest.

586793931[/snapback]

I agree i think it is good Microsoft are thinking more of a working OS rather then a profit one by releasing it far to soon.

Nice to see they are learning from there past mistakes. ( like Windows ME rushed out for year 2000, poorly made and more BSOD's then ever thought possible "

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

    • No registered users viewing this page.
  • Posts

    • Apple reluctantly forces strict new age checks on Texas users starting today by Paul Hill Apple will begin enforcing the Texas Age Assurance Law (SB 2420) following a recent court ruling that lifted an injunction on SB 2420. Starting June 4 (today), Apple will enforce strict age-verification and parental-consent rules for new Apple accounts created in Texas. This move will affect children under 18 who go to download apps or attempt to make in-app purchases. Apple previously expressed privacy concerns related to this law, but compliance is now mandatory for the company, nevertheless. Apple will use several APIs to follow the law. Principally, the Declared Age Range API will fetch the specific user age bracket (Under 13, 13-15, 16-17, or 18+) and a verification method. The Significant Change API (PermissionKit) will trigger a system dialog for parental consent if an app gets a major update or an age-rating shift. There is also a new property type in StoreKit that allows developers to automatically check when their app’s age rating has changed on a user’s device and then use the Significant Change API to request parental consent. Finally, App Store Server Notifications can be configured to tell developers when a parent revokes consent, blocking app launches. To ensure they are ready for these changes, developers must immediately use Apple’s sandbox testing environment to validate these APIs in their apps. For any developers out there finding this to be inconvenient, get used to it. Other regions, such as Utah, Louisiana, and Brazil, are looking at, or have implemented, similar rules.
    • They should show the onedrive recycle bin in a searchable manner and on app not just on the website
    • You looking at a phone or something? On my 4K HDR monitor it is frikking spectacular.
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      229
    3. 3
      Skyfrog
      72
    4. 4
      FloatingFatMan
      61
    5. 5
      neufuse
      54
  • Tell a friend

    Love Neowin? Tell a friend!