...The only thing I can think of is that while they were correcting and coding some other bugs, they may have inadvertently miscoded something else in the OS. In other words, 2 steps ahead in development, and one step back...
IMO, that's probably what did happened.
Any code change can have an unintended impact. It happens thoughout the development process (which is why developers invest in regression tests). In this case it seems like the problem was introduced in the GM. It's a bad time to make a mistake, but at least Apple caught it and gave themselves enough leeway to still get it out in November.
Last edited by a moderator: