New Claim of iOS 4.2 Launch on November 24th as Revised iPad Build Surfaces

[aperry]

As someone else said, get off your high horse...

because the first thing I do when I download an iOS beta is run to the forum and write "WiFi Works!"

Of course if a small percentage of people were having problems you see reports back to back

And if you are so smart, why release a gold master to testers at all instead of the general public? GM's ALWAYS go through the beta testers which is proper procedure.

My high horse? Sorry, I guess I had higher expectations for a device OS that represents $50 billion for Apple!

And why would they release a GM to developers? Um, I don't know, maybe so they can build/update applications with the new API's and get them to market concurrent with the OS release? Just a thought!

 

[cmaier]

My high horse? Sorry, I guess I had higher expectations for a device OS that represents $50 billion for Apple!

And why would they release a GM to developers? Um, I don't know, maybe so they can build/update applications with the new API's and get them to market concurrent with the OS release? Just a thought!

You make zero sense. "GM" doesn't mean "public released version." There's a reason it goes to the beta testers and only gets released if no show-stopper bugs show up from the beta testing. The process worked exactly like it was supposed to work.

 

[dguisinger]

My high horse? Sorry, I guess I had higher expectations for a device OS that represents $50 billion for Apple!

And why would they release a GM to developers? Um, I don't know, maybe so they can build/update applications with the new API's and get them to market concurrent with the OS release? Just a thought!

Yes, your high horse.
You are complaining that they are taking the time to F*N fix a BUG in a PRIVATE release before making it a PUBLIC release.

It needs to be said. Apple is doing the right thing, you are an impatiant self centered jerk.

Until December 1st comes around, Apple is still ON TIME

And the developer community already had a month with the developer build, no API changes were in the GM release. If you assume GM builds are perfect in every way, there should be no reason to seed GM builds to developers/testers before public release.

 

[sanford]

https://www.macrumors.com/2010/11/01/apple-releases-ios-4-2-golden-master-to-developers/

Unless the label "GM" in that screenshot means something else....

Greatly Maligned?

No, seriously, yeah it was GM, then. I still think it's up in the air whether Apple intended to release it today or next Tuesday or the 24th or whenever. I know rumored releases are often accurate but after years of being disappointed -- granted over features I'm only interested in or want, not need -- I just kind of wait around until I see that whatever is out. I sometimes do enjoy chatting about it the whole deal but I don't get worked about it anymore. Maybe I'm just getting old.

 

[lkrupp]

Reality Check

Can any of the bozos posting here about how lame it is for Apple to push back the release of iOS 4.2 provide a link in which Apple annouced iOS 4.2's release on ANY specific day? I thought not.

Can any of the pontificators who are pontificating about what has caused the alleged delay provide a link for such pontificating? No?

This entire thread is hilarious in its abject stupidity and lack of any relationship to reality. This is truly bizarro world.

 

[URFloorMatt]

My high horse? Sorry, I guess I had higher expectations for a device OS that represents $50 billion for Apple!

And why would they release a GM to developers? Um, I don't know, maybe so they can build/update applications with the new API's and get them to market concurrent with the OS release? Just a thought!

I'm going to agree with those disagreeing with you. I think your position is unreasonable. The release today or Tuesday (if that turns out to be incorrect) was nothing more than unsubstantiated rumor. Sometimes (even many times) rumors are incorrect. Apple said 4.2 would release on iPad in November. Until December 1 arrives without 4.2, there have been no "quality control" issues.

Now, the mess over AirPrint, that maybe suggests a legitimate QC problem, since Apple appears to be reneging on (or at least crippling) a new feature they previously announced.

 

[Mr Baldman]

Good. Take your time and do it right.

Exactly

 

[Spankey]

Didn't this same nonsense happen with Snow Leopard. The GM was out in the wild for days. Most were confident that what was out there was the GM until another build surfaced. It turned out the GM was the GM after all.

 

[cvaldes]

Can any of the bozos posting here about how lame it is for Apple to push back the release of iOS 4.2 provide a link in which Apple annouced iOS 4.2's release on ANY specific day? I thought not.

Can any of the pontificators who are pontificating about what has caused the alleged delay provide a link for such pontificating? No?

This entire thread is hilarious in its abject stupidity and lack of any relationship to reality. This is truly bizarro world.

Just another typical day at MacRumors.



Take your time, get it right, Apple.

 

[Aelton]

I presume that as with the other GM, it doesn't require your device to be registered with Apple?

 

[SnowLeopard2008]

Can any of the bozos posting here about how lame it is for Apple to push back the release of iOS 4.2 provide a link in which Apple annouced iOS 4.2's release on ANY specific day? I thought not.

Can any of the pontificators who are pontificating about what has caused the alleged delay provide a link for such pontificating? No?

This entire thread is hilarious in its abject stupidity and lack of any relationship to reality. This is truly bizarro world.

This post is exactly my thoughts right now. Apple didn't release an exact date for iOS 4.2, just "November". The rumors that it will be release today or tomorrow or any other specific days are just rumors. Until December 1st, Apple will have kept their promise of the November release date. iOS 4.2 betas and the GM aren't public, so you shouldn't have access to them anyway unless you are a developer.

 

[aperry]

You make zero sense. "GM" doesn't mean "public released version." There's a reason it goes to the beta testers and only gets released if no show-stopper bugs show up from the beta testing. The process worked exactly like it was supposed to work.

I make "zero sense"? How old are you? You sound fairly uninformed about software development.

The GM build is not intended for "beta testing", which is part of the reason why it's not another build labeled....."beta".

It's meant for developers to have early access to the release code for building and updating apps. Sure, a critical stop ship issue identified in this period is a bonus, but it also points to a large failure in their quality process. And back to my original point.....I'm surprised by it! That is all! It's just like the 3G performance issue, the bluetooth issues in 4.0, endless Exchange Sync issues in their initial support for Exchange, and the list goes on.

 

[pawelthegreat]

November 30th, guys. Remember that.

I agree.

 

[coleridge78]

I make "zero sense"? How old are you? You sound fairly uninformed about software development.

The GM build is not intended for "beta testing", which is part of the reason why it's not another build labeled....."beta".

It's meant for developers to have early access to the release code for building and updating apps. Sure, a critical stop ship issue identified in this period is a bonus, but it also points to a large failure in their quality process. And back to my original point.....I'm surprised by it! That is all! It's just like the 3G performance issue, the bluetooth issues in 4.0, endless Exchange Sync issues in their initial support for Exchange, and the list goes on.

The fact that you think these sorts of things are unusual tells me that you probably work in a small niche, on small systems. Granting that you really do work in code or QA, as you seemed to be saying.

What's changed with online distro is that Apple has the opportunity to release an updated "GM" rather than shipping out a disc that requires immediate foo.0.1 updates to be downloaded on purchase, which is how it used to go.

 

[aperry]

Now, the mess over AirPrint, that maybe suggests a legitimate QC problem, since Apple appears to be reneging on (or at least crippling) a new feature they previously announced.

Or a grand conspiracy with HP to help sell printers and avoid patent litigation, but that's for another day (mostly kidding!)

Anyway, true, the dates are unsubstantiated, but I think there's enough out there to suggest that today was the intended date. Combine that rumor, with the wifi issues in the GM build (which is fact), with newer rumors about the date being pushed due to those wifi issues. Obviously none of it is fact, but I think there's something there.

 

[newagemac]

Can any of the bozos posting here about how lame it is for Apple to push back the release of iOS 4.2 provide a link in which Apple annouced iOS 4.2's release on ANY specific day? I thought not.

Can any of the pontificators who are pontificating about what has caused the alleged delay provide a link for such pontificating? No?

This entire thread is hilarious in its abject stupidity and lack of any relationship to reality. This is truly bizarro world.

Ain't it strange how people (including rumor sites) somehow take rumors and speculation from some non Apple source and make it as though Apple said it. Then when it doesn't happen on that date, they see it as Apple "delayed" it. How can Apple delay something from a date they never announced? It's absolutely ridiculous. I mean seriously, Apple never announced in any way shape or fashion that iOS 4.2 would be released this week, next week, the 16th, 24th, or any of these dates being thrown around. The only thing Apple has said is that 4.2 would be released in November. Everything else is and always has been just rumors, speculations, and guesses.

There is no "delay" unless December comes and it has not arrived.

 

[cmaier]

I make "zero sense"? How old are you? You sound fairly uninformed about software development.

I'm 40 years old, and have >20 year of software development experience, and >10 years of microprocessor design experience. How about you?

The GM build is not intended for "beta testing", which is part of the reason why it's not another build labeled....."beta".

Wrong. The only people who can download and install it are the beta testers. GM indicates that Apple INTENDS to release it if there are no showstopper bugs, and that is all.

It's meant for developers to have early access to the release code for building and updating apps. Sure, a critical stop ship issue identified in this period is a bonus, but it also points to a large failure in their quality process. And back to my original point.....I'm surprised by it! That is all! It's just like the 3G performance issue, the bluetooth issues in 4.0, endless Exchange Sync issues in their initial support for Exchange, and the list goes on.

Again you are wrong. You clearly have no experience producing complex software or hardware products. Further, your original point WAS NOT "I'm surprised by it!"

 

[gwangung]

I make "zero sense"? How old are you?

Older than you. Considerably older.

 

[aprilfools]

this website (macrumors.com) needs a name change. It should be called Mobile Device Rumors. Nothing much more on macrumors in actually mac related. Please don't call me a troll. Most likely I have owned and used a mac before you were born.

 

[aperry]

The fact that you think these sorts of things are unusual tells me that you probably work in a small niche, on small systems. Granting that you really do work in code or QA, as you seemed to be saying.

It's an eCommerce development platform with literally millions of non-comment lines of code. Bugs get through all the time. Just not bugs that block major use cases and requirements (in this case, like wifi not working!).

Ok, that was a little "high horse". All I mean to say is that I'm surprised *this* bug got *this* close to being shipped and I believe it's telling (combined with other notable examples).

 

[JerzeyLegend]

I have been using iOS 4.2 on my iPad for a few days now, no issues at all.

I love it. It even fixed the mail issue I was having in 3.2.2 in which it would not send mail.

I have two wifi routers in my house, both of them connect fine.

Perhaps Apple should start selecting a group of users whom are not involved with development to beta test, this way they get outside results.

Then again, this would just lead to more and even more leaks, but what better why to critique your product than by having your target audience be the ones to test it for you. However i think once people see bugs they will flame/ridicule Apple and lose confidence in them.

 

[dguisinger]

It's an eCommerce development platform with literally millions of non-comment lines of code. Bugs get through all the time. Just not bugs that block major use cases and requirements (in this case, like wifi not working!).

Ok, that was a little "high horse". All I mean to say is that I'm surprised *this* bug got *this* close to being shipped and I believe it's telling (combined with other notable examples).

Out of curiosity...
When Microsoft is quoted as having 100 million lines of code in a very complex operating system.

How do you have millions of non-comment lines of code in an ecommerce platform? Tens of thousands, I'd believe. Millions??

 

[Aquinas]

Anyone has installed the patched GoldMaster 8C134b in Windows?

I downloaded the .dmg file but Windows cannot extract the .ipsw file because I don't have the utility to extract it. Anyone knows of a free .dmg extractor for Windows?

 

[coleridge78]

It's an eCommerce development platform with literally millions of non-comment lines of code. Bugs get through all the time. Just not bugs that block major use cases and requirements (in this case, like wifi not working!).

Wifi worked in most conditions for most people. What are you talking about? And no bugs that "block major use cases" [in some minority of conditions] have ever made it to release in the product you're talking about?

Not a chance.

You're clearly out of your depth, no offense.

 

[iSee]

8C134 --> 8C134b

LOL. I'm a software developer and here when a particular release is slated to be the final build but something goes wrong at the last minute we add a letter to the build number, just like this. (It's some internal political thing -- once development has promised that X37 will be the final build we don't want fail to deliver... so we can claim that X37b is still X37 even though it's really X38.)

It's funny to see Apple doing the same thing. I wonder if it's for the same reason