Do you all forget last year? I believe 9.2.1 was in beta at the same time 9.3 was in Beta.
https://www.macrumors.com/2016/01/14/apple-ios-9-3-public-beta/
Sure, but not impossible. I have no idea if the Twitter guy was real or not, but they could definitely do simultaneous betas. The date between releases could for lots of factors other than "we just feel like putting a week between them". (Not trying to be snarky)Yes, but 9.2.1 B2 was release 1/4/16 and public was 1/19/16. 9.3 B1 was release 1/11/16. There was a 7 day gap, not one day.
Sure, but not impossible. I have no idea if the Twitter guy was real or not, but they could definitely do simultaneous betas. The date between releases could for lots of factors other than "we just feel like putting a week between them". (Not trying to be snarky)
Nope, 10.3b1 will go out for devs tomorrow and 10.2.1b3 will go for public tomorrowSince theres no Public Beta build of 10.2.1 is it possible that iOS 10.3 Beta 1 could just be seeded to Public Testers First?
Right, like I said, it doesn't rule out 10.3. It may reduce the odds, but I don't think it eliminates them.Sure, if we were only talking iOS. But we have 3 other things that are receiving beta builds now. Watch, TV, Mac. Seems very unlikely to release a beta today and then a beta tomorrow for all 4 platforms. It probably won't happen until next week.
The one day gap just seems unlikely. To install 4 new betas on 4 different platforms to do it again the next day is not only annoying but kind of pointless. Especially if this is going to be the final build for all of these betas. What does releasing it to developers for 24 hours really do.
Developers have multiple testing devices. And this is a developer release.
I'm going to disagree. Developers want to run 10.2.1 on one device, and 10.3 on another. Not everyone updates. They will want to test on all firmware versions.What does that have to do with my post? A developer is not just going to install 10.2.1 and then not update to 10.3 in order to continue testing and building their apps. They are going to want to run the latest builds to make sure everything is working properly.
Since theres no Public Beta build of 10.2.1 is it possible that iOS 10.3 Beta 1 could just be seeded to Public Testers First?
Nope, 10.3b1 will go out for devs tomorrow and 10.2.1b3 will go for public tomorrow
This could make sense, 10.2.1 for public this week and devs get 10.3 tomorrow.What does that have to do with my post? A developer is not just going to install 10.2.1 and then not update to 10.3 in order to continue testing and building their apps. They are going to want to run the latest builds to make sure everything is working properly.
I'm going to disagree. Developers want to run 10.2.1 on one device, and 10.3 on another. Not everyone updates. They will want to test on all firmware versions.
The one day gap just seems unlikely. To install 4 new betas on 4 different platforms to do it again the next day is not only annoying but kind of pointless. Especially if this is going to be the final build for all of these betas. What does releasing it to developers for 24 hours really do.
This could make sense, 9.2.1 for public this week and devs get 9.3 tomorrow.
Agreed, definitely a possibility.This could make sense, 9.2.1 for public this week and devs get 9.3 tomorrow.
Giving the update to developers a day before the public beta is to make sure that there are no major issues during the install that brick your iPhone or anything like that as I'd assume most public beta users install these betas on their primary devices.The one day gap just seems unlikely. To install 4 new betas on 4 different platforms to do it again the next day is not only annoying but kind of pointless. Especially if this is going to be the final build for all of these betas. What does releasing it to developers for 24 hours really do.
Because 10.2.1 is going to be live before 10.3. Those that update to it (end users) are going to want their apps to work. Developers need to ensure their apps run as expected on it. You can't just skip an entire update. Devs need testing.Then why release the beta today? Whats the point of releasing the beta for 24 hours.
Giving the update to developers a day before the public beta is to make sure that there are no major issues during the install that brick your iPhone or anything like that as I'd assume most public beta users install these betas on their primary devices.
Because 10.2.1 is going to be live before 10.3. Those that update to it (end users) are going to want their apps to work. Developers need to ensure their apps run as expected on it. You can't just skip an entire update. Devs need testing.
This is true. When I do public beta testing, although I have 6 iPhones, I always install it on my daily driver.Giving the update to developers a day before the public beta is to make sure that there are no major issues during the install that brick your iPhone or anything like that as I'd assume most public beta users install these betas on their primary devices.
I didn't say the final will be released tomorrow. I'm talking about iOS 10.3. iOS 10.2.1 could be beta today, then 10.3 beta tomorrow. This would not be unheard of.I think you are missing something. Why release todays beta if its the final version that might be released pubically tomorrow.
This is true. When I do public beta testing, although I have 6 iPhones, I always install it on my daily driver.
[doublepost=1483988352][/doublepost]
I didn't say the final will be released tomorrow. I'm talking about iOS 10.3. iOS 10.2.1 could be beta today, then 10.3 beta tomorrow. This would not be unheard of.
Actually I meant that the public could beta test 10.2.1 this week while devs can test 10.3. But I suppose it works either way, if Apple wants to test it one last time they have to go to the devs first.I think you are missing something. Why release todays beta if its the final version that might be released pubically tomorrow.