There are other things to fear in this world sirwhen i updated to 10.2.1 i was hopfull that my iphone would be better. but it become laggy....i fear to update to beta 4
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.
The iOS 10.x.x Beta Speculation Thread
- Thread starter gwhizkids
- Start date
- Sort by reaction score
Most likely not. I suspect they are closing the CIA exploits in this version so most likely another beta maybe next week with those fixes.
http://www.zdnet.com/article/apple-...related_listing&ftag=TRE17cfd61&bhid=89370938
But 10.2.2 would mean leaving the developments so far on 10.3, and reverting to 10.2.1 and starting development on that. Doesnt appear logical.
Realistically there are always "still bugs". Given that we are close to 10.3 being finalized chances are they'll add any security patches to that if really needed. Then again, who really knows.
Why? Close the exploits with 10.2.2. get it out to the public. Same for 10.3 and iron bugs out.
Last edited:
If we supposedly lived this long with those exploits why suddenly rush it over a matter of a few weeks at this point?
And given where we are it's a good possibility that to get them out in a 10.2.x release would likely take about as long as getting them out in 10.3 if they wanted to address them at this point (unless they aren't as close at it seems to being done with 10.3).
But, like I said before, anything is a possibility, realistically speaking, but doesn't seem like there's much making a 10.2.x release "most likely" at the moment. Ultimately we'll find out in the next weeks.
Can anyone comment on the significance of increment in the version number of Betas.
Does change in one character imply one change in the software? for example, the difference between 14E5230d and 14E5231d is just one change in software.
Its just builds. I don't think there is much to read into it (like if the letter changes vs the number and so on). I have never come across an explanation for the different letters and what not. But only a handful of times in the history of iOS has a final public release had a small letter at the end. So thats typically a good way to determine if there will be another build.
Explanation of iOS build numbers
14 = Major version. Here it says it is an iOS 10 build. '13' means iOS 9 so on so forth.
E = Minor version. First major version starts with 'A' which is x.0 launch release. iOS 10 (14A403). It is not necessary to be a 10.x point release to increment this it may be 10.x.x release. Usually Apple increment this when kernel version changes.
5 = It means that this build is not prepared for public release. Builds have this in build number will not release as stable build.
269 = Actual build number. It means that it is the 269th build of iOS 10.3. There may be a lot of code changes. Generally Apple has a new build everyday. And Apple tests these builds 1 week before releasing it. So, 14E269a went to Apple test team last week to test if there is a major bug. If there is see the next:
a = Revision letter. If Apple test team find bugs, they sends a report to engineering team. Engineering team tries to fix some of them and increments the revision letter. It looks like test team hasn't found any bugs to be fixed before releasing it. So, Apple released to us.
So what can we understand from today's beta?
The build number has '5' before the actual build number. Hence, this is not the build we will see when Apple releases iOS 10.3 stable. I personally expect one more beta, but it may have '5' before the actual build number. Last beta of the iOS 9.3 release is iOS 9.3 beta 7 and its build number is 13E5234a, public release iOS 9.3 build number is 13E234. It means that Apple hasn't prepared beta 7 build as final release but it looked promising, so they released it as it was.
See?
iOS 9.3 beta 7 = 13E5234a
iOS 9.3 final = 13E234
We do not know if final release is same as beta 7. Actual build numbers are same but revision letter may be 'b' instead of 'a'. But very minor thing changes in revisions.
Can revision letter say how good build is?
Well... I think, yes. Take a look at iOS 10.3 betas:
iOS 10.0 beta 1: 14A5261v
Do you see 'v'? Yes, Apple has a, b, c, ... v revision builds before releasing the first beta of iOS 10 to fix some minor bugs before introducing shiny iOS 10 to us.
iOS 10.3 beta 1: 14E5230e
iOS 10.3 beta 2: 14E5239e
iOS 10.3 beta 3: 14E5249d
iOS 10.3 beta 4: 14E5260b
iOS 10.3 beta 5: 14E5269a
It can be clearly seen Apple test team found less and less bugs and reported to engineering team. As result revision letter comes close to 'a' (finally we see 'a') as final release approaches.
One last note, revisions generally happen in 1 or 2 day(s). It is pointless to spend much time in one build, because they have a new one already. I mentioned that Apple sends builds to test team 1 week before. So, when test team sent the report of 14E5269a, engineering team probably was working on 14E5272a. Moreover, iOS 10.3 is not the only branch they are working on. They are working on iOS 10.3, iOS 10.4, iOS 10.4.1 and iOS 11 at the same time. So, it is very complicated actually.
What's next?
I expect one more build as:
iOS 10.3 beta 6: 14E5275a
iOS 10.3 final : 14E275/14E276
How do I know these?
I am a software engineer
Most companies use build systems like Apple does, and the logic is same. For example,Latest Google Chrome release: 56.0.2924.87
56 = Major
0 = Internal version. It has no purpose.
2924 = Minor
87 = Revision
I hope I've explained the build number thing as clear as I could.
Last edited:
Thanks, but this seems contradictory. "5" means not a public release build, but then you say "I personally expect one more beta, but it may have '5' before the actual build number."
The final beta more times than not is the final build (as of the last couple of years). So if the next build has a "5" it can't be the final, no?