Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There isn't a code release in history without bugs. This is very odd. Has to be a huge security issue to stop a release.

No, it does not. Companies that develop software classify bugs according to severity level. A top severity bug could be one that disables or seriously compromises a significant feature without reasonable workaround. It does not have to be a security problem. Bugs in the top severity level would automatically delay release.
 
Wow. All this praise for Apple not releasing something with a major bug. It's like thanking a mugger for taking your jewelry and wallet but letting you keep your shoes.

Seriously folks... Apple is being kind here? It's incompetence.
 
Well I'm pissed off, I guess it's better they're admitting there's an issue now though before screwing up a release. May as well just go to the GM I guess now.

Yes, why not download the GM which they've just confirmed has a bug thats stopping them releasing it to the public because you can't bear to wait a couple extras days...
 
  • Like
Reactions: vmistery
You don't realize the complexity of an OS software release. There are hundreds of developers working on the os. There are 1000s of bugs all the time (obviously most of them are not showstopper bugs and are deferred to later releases). There is most certainly round the clock testing going on done by testing teams around the world. Fixed bugs can cause regressions that need to be found. Even with only critical bugs getting fixed and make it into the release code line (and I am sure they will be code reviewed and need high up approval so close to release time), and even with full testing there are always holes in your test plans. Things can slip through. Also timelines are extremely tight. Yes in an ideal world they would have months too harden a GM release, but in reality it's just a couple of weeks.. So things can slip out. It's all about risk management and improve testing for the next round.
Spoken like a software quality engineer! Where I used to work, the bugs came in 5 classes, and class 1 and 2 were show stoppers, class 3 (bugs with work-arounds) were reviewed for fix plan prior to beta.

The worst thing about long release times was the feature creep... "Oh yeah, we can put that in there too!" Drew groans from the software engineers.
 
Wow. All this praise for Apple not releasing something with a major bug. It's like thanking a mugger for taking your jewelry and wallet but letting you keep your shoes.

Seriously folks... Apple is being kind here? It's incompetence.

Clearly, you're not familiar with software developement.
All software contains bugs. EVER.

But some bugs are minor, like visual bugs. And some bugs are major, like exposing your health data to the entire world (for example).

So, now explain me, how happy you would have been, when Apple released a buggy watchOS 2, when you are unable to downgrade? Aha. See!
 
  • Like
Reactions: ErikGrim
I've been running the 2.0 GM since it was released and haven't experienced any bugs. Wonder if it's security related, or related to native 3rd party apps.
 
let's be honest, this watch does nothing more than show notifications right now
Mine shows when my next meeting will be, the weather, tracks my workout activity which I do daily, gives my bank balance in a glance, provides a timer for soccer games, the time and date, and among other things allows me to pay in places that take ApplePay which I try to use on purpose. Yea, and it will show notifications.
 
  • Like
Reactions: ErikGrim
let's be honest, this watch does nothing more than show notifications right now
Mine does quite a bit, actually. Then again, I'm a developer with the wOS 2 GM running.

I'm sure your watch also tells the time, and has the suite of fitness features working as well. It still works with other apps, too - perhaps not as fast as you'd like. Still, that's more than 95% of watches in the world.

You're whining... you've done nothing but whine in this discussion.

They found a bug. It happens. Good on them for checking again before making it available to millions of people.
 
So, I have been on several versions of the 9.0 beta and the 9.1 over a week and have never had any problem with watch notifications. Is it just some specific apps, or all notifications?

can anyone else corroborate this seemingly unfounded rumor or statement from the above poster?

On many versions of the 9.0 beta my notifications were spotty. Most of the time I'd receive email notifications, hardly received any text notifications. Another annoyance was the fact that my text history wasn't being updated on my watch from about beta 3 or so onwards. On 9.1 I haven't had any issues so far. Pretty much all other notifications were working fine as I recall.
 
accept for we dont know when the watch will be updated because of this bug. it could be tomorrow, it could be a week later.
I want Watch OS 2 as much as anyone else, but am willing to wait until they sort out the bugs.
 
yes. and i'm an apple fanatic. but catching major bugs at GM is a depature from best practices in the beta process

Lol. "Best practice" specifically refers to policies and procedures, not results. QE testing should continue in parallel with Beta testing; not be replaced by Beta, as you (I'm sure inadvertently) imply.

Anyone who actually knows anything about software development knows that it is possible that a fix of a bug discovered during Beta phase could in itself cause a Severity 1 error.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.