Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Well, a revised Beta 2 isn’t part of the normal cycle and wasn’t planned for….. I’m not saying there definitely won’t be a DB3 this week, just saying that we should not be relying on the usual cycle. The iOS 14 and 15 betas have showed that Apple will buck their trends. I’m keeping an open mind, after being burnt by sticking to what Apple usually do.

The trend with PB was it came a week after the DB, so DB3 this week with PB2 next week would be the cycle for this point in the beta process, so you are saying Apple will buck that trend by following the trend later on in the x.0 beta process?

Your post is slightly contradictory mate.

Damn…I need that stupid beta chart handy.

Maybe I AM being too premature.
 
Damn…I need that stupid beta chart handy.

Maybe I AM being too premature.

Screen Shot 2021-07-05 at 8.11.30 AM.png
 
Regardless of when the next beta is released, now’s probably a good time to remind everyone to save the .ipsw file for each beta in case there IS some bug that makes “things” unusable for you. If Apple follows what they’ve done quite literally every year prior, each beta build will remain in signing status so you can roll back to an earlier beta if needed.
 
  • Like
Reactions: srbNYC and Pearsey
Thanks…and now I need PB releases related to DB releases.

I’ll find it.

A year ago I proposed a better tracking system for beta releases than the thinkybits chart. An actual spreadsheet of beta drop and release dates, for both public and developer betas. I was roundly criticized for this crazy suggestion because we have the all-good thinkybits chart so it went nowhere.
 
Regardless of when the next beta is released, now’s probably a good time to remind everyone to save the .ipsw file for each beta in case there IS some bug that makes “things” unusable for you. If Apple follows what they’ve done quite literally every year prior, each beta build will remain in signing status so you can roll back to an earlier beta if needed.
Best to wait roughly 1 hour until the MacRumors beta task force did their thing and verified the integrity of a build.
 
  • Like
Reactions: Ansath
Best to wait roughly 1 hour until the MacRumors beta task force did their thing and verified the integrity of a build.
There’s been a few times over the years where some apps like Mail or Maps don’t work right, at least for me, and just “updating in place” over itself with a prior beta puts you on that prior build. Some times those types of regressions aren’t seen for days after updating.
 
A year ago I proposed a better tracking system for beta releases than the thinkybits chart. An actual spreadsheet of beta drop and release dates, for both public and developer betas. I was roundly criticized for this crazy suggestion because we have the all-good thinkybits chart so it went nowhere.
A thought...

@BlankStar ...can you make your original post a Wiki so we can add a section at the top that confirms actual release dates for both DB and PB for iOS 15 before we forget?

At least then, we have something to go back to that can be collated at some point.
 
A thought...

@BlankStar ...can you make your original post a Wiki so we can add a section at the top that confirms actual release dates for both DB and PB for iOS 15 before we forget?

At least then, we have something to go back to that can be collated at some point.
There is a release date history, just google „iOS xx.x public beta y release“ and you should get a gazillon articles shouting it out into the world wide web.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.