Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.

Alhagar

macrumors 6502
Apr 19, 2015
423
255
I believe that after beta 5, we'll move to three-week cycles.
I realize that you are joking, but this thread is interesting in that it highlights the common conflation in these forums between “believe/think/know” and “hope/wish/want”.
 
Last edited:

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
I believe that after beta 5, we'll move to three-week cycles.

I realize that you are joking, but this threat is interesting in that it highlights the common conflation in these forums between “believe/think/know” and “hope/wish/want”.

It's not a joke and there is possible truth to it. Look at past history. Most betas stop at 4-6 and there is a 3 week gap until the GM.

He may be joking. But it's not unrealistic.
 

uandme72

macrumors 68020
Mar 2, 2015
2,075
684
Assuming it is to be released next week on 7 august, when do people think the build will be frozen for it to be released on 7?
In other words, what is the date by which the reported bugs till that date are expected to be fixed/ incorporated in the next beta of august 7?
 

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
Assuming it is to be released next week on 7 august, when do people think the build will be frozen for it to be released on 7?
In other words, what is the date by which the reported bugs till that date are expected to be fixed/ incorporated in the next beta of august 7?
Its really hard to guess when it comes to that. Apple is on builds that never even get seeded to developers, they only remain alpha stage builds. You can tell this by the revision letter of the build number. This build has a little g, so this one build went through 7 stages before it was seeded. In addition to that, Apple is probably working on the GM as that needs to be seeded for production of new devices. So most bug fixes that are reported in July, won't be incorporated in until the final release in the fall.

Most of the fixes in August 7th beta would have been reported in June. Because of how many builds they are ahead internally. Nothing reported from the last 2-3 weeks will be in this build.

Hopefully that answers your questions.
 

batting1000

macrumors 604
Sep 4, 2011
7,464
1,874
Florida
Its really hard to guess when it comes to that. Apple is on builds that never even get seeded to developers, they only remain alpha stage builds. You can tell this by the revision letter of the build number. This build has a little g, so this one build went through 7 stages before it was seeded. In addition to that, Apple is probably working on the GM as that needs to be seeded for production of new devices. So most bug fixes that are reported in July, won't be incorporated in until the final release in the fall.

Most of the fixes in August 7th beta would have been reported in June. Because of how many builds they are ahead internally. Nothing reported from the last 2-3 weeks will be in this build.

Hopefully that answers your questions.

Lots of speculation here...this is probably false. I've gotten replies to my reports saying changes in this build may have fixed this, or whatever the actual wording is...and those are in response to bugs from the previous beta. I highly doubt they're 2-3 betas behind when it comes to incorporating bug fixes. If that was the case, we'd still have all of beta 1's bugs lol

There's less than 5-ish weeks left of Apple working on iOS 11 because it locks ahead of the September event
 
  • Like
Reactions: trizzil

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
Lots of speculation here...this is probably false. I've gotten replies to my reports saying changes in this build may have fixed this, or whatever the actual wording is...and those are in response to bugs from the previous beta. I highly doubt they're 2-3 betas behind when it comes to incorporating bug fixes. If that was the case, we'd still have all of beta 1's bugs lol

There's less than 5-ish weeks left of Apple working on iOS 11 because it locks ahead of the September event
Just because we report a bug in beta 1, doesn't mean that they hadn't already fixed in beta 2. Just because someone reported it, does not mean Apple didn't know about it beforehand. Apple is always 2-3 builds ahead internally, whether they are alpha or beta seeds is unknown. But my information is not made up, that information was given to me by engineers in the past.
 

uandme72

macrumors 68020
Mar 2, 2015
2,075
684
Its really hard to guess when it comes to that. Apple is on builds that never even get seeded to developers, they only remain alpha stage builds. You can tell this by the revision letter of the build number. This build has a little g, so this one build went through 7 stages before it was seeded. In addition to that, Apple is probably working on the GM as that needs to be seeded for production of new devices. So most bug fixes that are reported in July, won't be incorporated in until the final release in the fall.

Most of the fixes in August 7th beta would have been reported in June. Because of how many builds they are ahead internally. Nothing reported from the last 2-3 weeks will be in this build.

Hopefully that answers your questions.
Thats pretty much clear.
However, that leaves one question unanswered. There are many bugs reported since January 2017, yet they are not fixed till now. Does that imply that - bugs reported later than July will definitely not be fixed till September, but that does not mandate bugs reported in January will get fixed by July.
 

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
Thats pretty much clear.
However, that leaves one question unanswered. There are many bugs reported since January 2017, yet they are not fixed till now. Does that imply that - bugs reported later than July will definitely not be fixed till September, but that does not mandate bugs reported in January will get fixed by July.

It depends on if Apple is aware of the bug in iOS 11, even before it was reported. They are aware of bugs, without a doubt. They are seeding betas knowing their are bugs in them. Thats why they include "known issues" in release notes.

Bugs that have been reported in Jan. might never get fixed because they don't deem them "major". Look at the safari history bug for example. They don't consider it a major bug so its been present for 10.3.2 and 10.3.3. But the most amount of bug fixes take place between now and the GM, as they are doing their best to perfect that. Within 2 weeks of iOS 11 coming out, expect a 11.0.1. Pretty much happens yearly. Last minute fixes that they couldn't get into the GM.
 

uandme72

macrumors 68020
Mar 2, 2015
2,075
684
It depends on if Apple is aware of the bug in iOS 11, even before it was reported. They are aware of bugs, without a doubt. They are seeding betas knowing their are bugs in them. Thats why they include "known issues" in release notes.

Bugs that have been reported in Jan. might never get fixed because they don't deem them "major". Look at the safari history bug for example. They don't consider it a major bug so its been present for 10.3.2 and 10.3.3. But the most amount of bug fixes take place between now and the GM, as they are doing their best to perfect that. Within 2 weeks of iOS 11 coming out, expect a 11.0.1. Pretty much happens yearly. Last minute fixes that they couldn't get into the GM.
So that means the most bugs can be fixed just before a new major release. So we must report as much as possible now rather than after release of a 11.0.1 ?
 

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
So that means the most bugs can be fixed just before a new major release. So we must report as much as possible now rather than after release of a 11.0.1 ?
I believe so, yes. More that is reported now, is better for the GM and 11.0.1 release. Once 11 is out, bug fixes move much more slowly. I reported the Safari Keyboard bug in iOS 10.0 beta 2. It wasn't fixed until 10.2 Beta 1. Over 10+ builds later. I really wish I could know how Apple prioritizes bugs.
 

uandme72

macrumors 68020
Mar 2, 2015
2,075
684
I believe so, yes. More that is reported now, is better for the GM and 11.0.1 release. Once 11 is out, bug fixes move much more slowly. I reported the Safari Keyboard bug in iOS 10.0 beta 2. It wasn't fixed until 10.2 Beta 1. Over 10+ builds later. I really wish I could know how Apple prioritizes bugs.
If the bug fixing slows down after 11, what does the huge army of developers do if not be fixing bugs?
 

Mlrollin91

macrumors G5
Nov 20, 2008
14,172
10,181
If the bug fixing slows down after 11, what does the huge army of developers do if not fixing bugs?
Continuing working on the next version of iOS? I'm sure iOS 12 is already in the works now. They still fix bugs, but most of the bugs remaining are not that important to functionality or are only cosmetic, so its not at the top of the list. They may also be working on new features for X.1 or X.2 builds.
 

stulaw11

Suspended
Jan 25, 2012
1,391
1,624
Buh buh buh, iOS 10 this and that (with fingers in ear lalala);

51LwtXlb4jL.jpg


:rolleyes:

The reddit guy is 4 for 4 and CLEARLY has some insider info to be that accurate. He said 8/7.


Neblinio 1 point 2 hours ago

/u/Madscotsman35 is it coming on August 7th?
 

mariusignorello

Suspended
Jun 9, 2013
2,092
3,168
Beta 5 will be the last of the two week betas. Then we should start seeing them weekly or almost every 7 days. We’re getting close to September.
 

sbailey4

macrumors 601
Dec 5, 2011
4,571
3,253
USA
Bluetooth does increase battery drain, not as much as it used to in the past, but its still there.
Yes but as stated, its negligible and turning it off and on all day doesn't really help with any noticeable battery life for the day. Again just by being on. If its being used thats a different discussion but still not bad.
[doublepost=1501524887][/doublepost]
To each their own. I’m not going to leave on something that I never use anyway, especially if I may get even the smallest amount of battery savings. Do that with multiple features that you don’t use and it may add up to be significant.
Yeah if its never used at all then correct. But folks turning wifi on and off and BT on and off all day probably use more battery firing up the screen to turn it off and on than the feature itself uses to start with. Think thats the point. And BT is so minimal it really is useless worrying about it IF you use it ever or even regularly. If never, then yeah may as well switch it off.
[doublepost=1501526267][/doublepost]
If the bug fixing slows down after 11, what does the huge army of developers do if not be fixing bugs?
They continue working on iOS 11.0.2 for the speaker in December. Among other things.
[doublepost=1501527625][/doublepost]I find it amusing with the predictions methodology that folks use. They based predictions for iOS 10 and 10.x on iOS 8 and 9 history and it was almost always different because iOS 10 "did things differently" and folks were always blindsided because "they have never done that in the past". Now they say you cant base iOS 11 on iOS 10 because 10 was so different but then go back to using the past iOS 8 and 9 history to predict what 11 may do. Even though it was proven you cant base the next one from past history. And base it on what date WWDC was and when they think the release date is and how many betas there WILL be all because of what iOS 8, 9 and or 10 did or didnt do and how many betas they had. :confused:

Of course all that has to be used to speculate on a future iOS because thats all we have to go on but interesting still how the thoughts of the process change from one to the other and definitely amusing to sort thru the contradictions to speculate what may happen. Heck there could be bi weekly betas and 20 of them and no release until December when a theoretical iPhone 8/10/Anniversary may or may not show up just in time for the holiday season! lol
 
Last edited:
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.