It just seems odd that they didn’t release ios11 and macos high sierra public betas during same day...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 11.x.x Release Speculation Thread
- Thread starter LoveToMacRumors
- Start date
-
- Tags
- ios 11.3 iphone x update ios
- Sort by reaction score
- Status
I think they did this last year. Sierra came out after iOS 10. They definitely did that with iOS 9 and El Cap.
Wouldn't it make more sense to stagger them so they aren't overloading their servers with people downloading the new release?
I'm even thinking next Wednesday may prove difficult due to Monday being observed as a holiday by a lot of companies and Tuesday being the actual holiday, but who knows! Hopefully on or before next Friday at the latest... really would like a working app store backend again!
i think they released on the day after the 4th last year.
That said, the last two years have shown that predicting on past performance isn't a good measure anymore. I'm not betting against Monday and Tuesday anymore, even with the holiday.
It definitely will not be out on the 4th. The third, I'm unsure. A lot of big companies are closed for the 4 day weekend, so it only makes sense Apple would be as well. Besides if they released it Monday, that's only 12 days since beta 2. I think they intentionally released it last Wednesday to go 2 full weeks until the next one.
Last edited:
I'll go with the 6th. Gives everyone a chance to shake off the hangovers from the long weekend!
Realize that a simple holiday like July 4th means little. It's not like Xmas time where they get a week off. Theyve been working on DP3 since they day DP2 released; maybe even a few days earlier.
It's not like they're scambling on the day before the release to finish coding. Maybe at most compile and test the release for installation bugs, but that's about it.
There's no reason it cant be 7/5 or 7/6 still. It wont be 7/4 and likely not 7/3; they typically dont release the day before a holiday in case there is some major issue.
It's not like they're scambling on the day before the release to finish coding. Maybe at most compile and test the release for installation bugs, but that's about it.
There's no reason it cant be 7/5 or 7/6 still. It wont be 7/4 and likely not 7/3; they typically dont release the day before a holiday in case there is some major issue.
I really would be fascinated to see how this really works.
Scenario 1: There's one guy who pushes the "Release Beta!" button, yawns and returns to his normal activities (probably including reading beta release prognostications from @mrollin91 and crossing those dates//times off the official Release Beta time candidates for upcoming betas) or
Scenario 2: There is a dramatic countdown timer in Beta Release HQ, counting down the minutes and seconds to Beta Release time. As the appointed time arrives, sirens wail and red lights flash as the Beta Release Moment is reached. As the D+ clock counts up from the release point, Apple Engineers sit poised over their workstations waiting for bug reports to come pouring in. The guys at the Battery and Lag Stations, however, have to filter their inboxes to prevent any responses from reaching them until 24 hours of battery burn-in and re-indexing is complete.
Obviously, both scenarios tongue-in-cheek, but obviously, there is some method to Apple's processes...or, there's not, or at least not as much as we'd give them credit for. Its never as interesting behind the curtain as we imagine.
Likely neither.
The code is likely compiled into the necessary package/file type for OTA (and the ipa for the Dev Site) and loaded into their servers which propagate other servers (the beta is not just hosted on 1 server across the world to download) and a time is set when it goes live across all of them.
I HIGHLY doubt someone is sitting there with a countdown clock as technology handles all of that timing no matter when the final version is loaded in.
More than likely all finalization is done before the day the beta is released, maybe the early morning of at the latest, to allow for a chance to test the compiling and delivery before going public.
You have to remember how much goes into this to make sure not only the update file itself is good, but both the OTA and ipa via itunes installs without errors.
The code is likely compiled into the necessary package/file type for OTA (and the ipa for the Dev Site) and loaded into their servers which propagate other servers (the beta is not just hosted on 1 server across the world to download) and a time is set when it goes live across all of them.
I HIGHLY doubt someone is sitting there with a countdown clock as technology handles all of that timing no matter when the final version is loaded in.
More than likely all finalization is done before the day the beta is released, maybe the early morning of at the latest, to allow for a chance to test the compiling and delivery before going public.
You have to remember how much goes into this to make sure not only the update file itself is good, but both the OTA and ipa via itunes installs without errors.
Of course, I think you're correct. The more interesting thing would be the engineering meetings where they decide "go"/"no go" and what's behind that thinking. I'm sure they have a nice GANNT chart posted somewhere with all their release milestone dates with the big black diamond for the GM date.
I can't see beta 3 being released next week as we got Beta 2 updates this week...
I hope for the 10.3.3 final, tho.
I hope for the 10.3.3 final, tho.
Except all DP2 Update 1 fixed was downgrading on certain devices so that they could release a Public Beta.
There were no official changes, and next week is 2 weeks since Beta 2 released if they keep a 2 week schedule
Yes, but for the public beta it'll be a week between the first public beta and the second one, so I'm not sure if they gonna do that... we'll see.
Yes, but for the public beta it'll be a week between the first public beta and the second one, so I'm not sure if they gonna do that... we'll see.
That doesn't mean they can't release developer beta 3 next week
Now they'll release new dev and public betas at the same time (with a day or two between them, probably), so it just doesn't make sense to release a new dev beta and delay the public beta with a week. We'll see.That doesn't mean they can't release developer beta 3 next week
Obviously nothing today. I'm going to stick with DB3 on Weds and PB2 on Thursday.
Hello folks.
Predictions for this week:
Apple will release an DB 3 and PB2 . Thats it
Predictions for this week:
Apple will release an DB 3 and PB2 . Thats it
Feels like it
Took about an hour to download 500Mb today for my watch (does not include install) but my Xbox downloaded 22GB in 20 minutes
Apple Watch is always slow. Even for 5MB. Thats because its downloaded to the phone via WiFi and then transferred to the watch. Its a two step process, and thats why it takes what seems like forever compared to iOS or macOS updates.
- Status