Trust me, they don't know. Unless you spoke to an Apple Rep from the iOS team (and they would be hung for committing to a date)
Please tell me you know November 31st is not a valid date LOL.
Trust me, they don't know. Unless you spoke to an Apple Rep from the iOS team (and they would be hung for committing to a date)
I think a better update to be watching, and a better indication of when our iDevices can be updated officially to 4.2, will be when the Apple TV is updated. Surely it has to be updated first, for AirPlay.
We live in an amazing time, and people take it for granted.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)
Jesus Christ. Please just release something and THEN release the app / issue specific patches. I'm running 3.2 and don't have a dev account, and I can't stand these delays any longer.
I think a better update to be watching, and a better indication of when our iDevices can be updated officially to 4.2, will be when the Apple TV is updated. Surely it has to be updated first, for AirPlay.
I hope they fix printing, because it doesn't work at all for me.
I cannot:
1. Print wirelessly to my HP printer.
2. Print through iTunes and my Mac to that printer.
Has anyone confirmed that it will be updated? I find it weird that they don't release dev builds of Apple TV firmware
An apple rep told me 4.2 would be released November 31st
Yup.
iPad 3G was promised in April - and showed up 4/30/10 at 5:00PM, just seven hours to go.
We've got almost a half-month to go and some nutcases are screaming "It's late!"
Yes they do unless if they want to now look inconsistent. If the bugs affected everyone then they would have simply held back 4.2 and released another GM "BUILD". The versions 4.2, 4.2.1 are "RELEASE" versions. They have to release 4.2 if they intend on releasing 4.2.1.No they don't "HAVE" to
Amazing the impatience of ppl.
Apple has more to consider than those like us who peruse Apple news etc... How many of the 150m or so iOS users even realise there is an update coming... The number will be a lot smaller than u think
The os is getting more complex and complexity = more bugs. At least they're trying to prevent show-stoppers as the bad press they would get from a bad one is much worse than a delay reported only in the Apple blogosphere.
We still have almost 2 weeks of November left anyway.
You make me sad for humanity. We have all this amazing technology, we can do such incredible things. I mean you have a tablet computing device that is more powerful than the computer used to launch humans into space. You can communicate with everyone instantly and play mindless games while on the toilet at a gas station in the middle of nowhere.
We have all this, and yet you still aren't happy. You get frustrated over such a pointless thing like being able to put your virtual crap into folders so you can feel better about using this amazing piece of technology.
You are spoiled and you don't realize how awesome it is to have what you have. You need to chill out and just enjoy it. When 4.2 hits it will be even more enjoyable, but not having it doesn't make it any less incredible.
Once you've named a build of a particular version the 'golden master', you can't really reuse the same term for another build of the same version!
Why would they? There is no SDK (yet) for Apple TV, and therefore no developers who need to test their apps against it.
Didn't they release something right before Thanksgiving a few years ago? I remember going out of town for Thanksgiving and remebering to take my laptop so I could update my phone that night when I got where I was going.
I'm getting sick of this waiting! If I can't put Angry Birds HD and Angry Birds Halloween HD in a folder named "Angry Birds Games" by this evening I'm going to flip the hell out!!!
You can have a GM release candidate BUILD and a GM release BUILD. You can have multiple RCs or GM RCs but only one GM release. Generally, you never release a x.x.x version without first releasing a x.x version first.I agree wholeheartedly, but man, you'd be surprised (or not, depending on what you do for a living) at how often people do.
Getting a chuckle about all the twisted panties around here.
k.
(release engineer)
Here here...LOL
Yes they do unless if they want to now look inconsistent. If the bugs affected everyone then they would have simply held back 4.2 and released another GM "BUILD". The versions 4.2, 4.2.1 are "RELEASE" versions. They have to release 4.2 if they intend on releasing 4.2.1.
Apple has often released a 10.x release and quickly released a 10.x.x patch update soon after.
They can have multiple GM candidate 4.2 builds but once they start releasing 4.2.1 for testing to developers, that means that 4.2 is going out the door otherwise, they would have just release another 4.2 GM with the bug fixed rolled in.
I am a software developer and so I can tell you that teams will release a release candidate to UAT and then release a version such as 8.x to production. If bugs are found which are critical after it has been sent for release, a patch like 8.x.1 has to be developed, released and installed even if it ends up being installed almost immediately after the 8.x release.
Here is an illustration of how the majority of software development works:
1. A release scope is developed and given either a major or minor version increment.
2. That release is developed and tested by QA.
3. That release is tested in UAT or beta testing.
4. That release has multiple "builds" ie.
8.1 build 1
8.1 build 2
...
8.1 build 351 (RC)
....
8.1 build 401 (GM) Released to production with testing continuing.
Bugs found
8.1.1 build 1
...
8.1.1 build 23 (GM) Patch released to production.
8.1 installed if no show stoppers found.
8.1.1 installed same day if show stoppers found in original release, otherwise installed later.