But if they squash some bugs in 18.2.1 that never were fixed before 18.3 B1, wouldn't they be pushing that to the beta? They wouldn't want to leave those bugs in over the holiday. I am just not sure they have time for it though. There were people here saying that a lot of Apple employees left the office on Tuesday for the holiday, which means they don't have the full team.
Bug fixes can be addressed in the current release and in the future beta point update. It's bugs specifically related to things in the .3 update that wouldn't be addressed.
Oh yes for sure, but I wouldn't think Apple would want to fix things in 18.2 that carried over 18.3, but only release those to 18.2 and leave 18.3 hanging for 2 or more weeks. If it were a week, I could understand, but two over a holiday seems like a lot.
I would assume they’d want a more stable release out in the wild over the long holiday break, as opposed to just shelving some could be basic fixes for a month or so.
Oh I agree, I don't know if they still have the resources to push out right now. The thought around here was that something would need to be out by no later than Tuesday before people leave the office. If not, or than likely it isn't happening.
): Apple doesn’t do their software development on an ad hoc basis. If they intend to release an 18.2.1 before the holidays and vacation time, then they put it on the schedule and got the necessary work done before people leave/left. And you can be sure that if an urgent 18.2.1 were necessary (but not originally programmed to be part of the release cycle), they have a skeleton crew of engineers around who can get it done. And they will call people in if needed (as in a super serious zero day bug).
That was my point. There is no emergency that needs to be addressed, and if they have not released it yet, it's not happening. Like you said, this was planned way in advance.I know I sound like a broken record (for those under 40, look it up): Apple doesn’t do their software development on an ad hoc basis. If they intend to release an 18.2.1 before the holidays and vacation time, then they put it on the schedule and got the necessary work done before people leave/left. And you can be sure that if an urgent 18.2.1 were necessary (but not originally programmed to be part of the release cycle), they have a skeleton crew of engineers around who can get it done. And they will call people in if needed (as in a super serious zero day bug).
Large organizations don’t leave stuff like this to chance. It is all meticulously scheduled, working back from when iOS 19 has to be released to manufacturing.
Yass Apple give us the alpha access ♡
