/article-new/2011/09/ios5.jpg?lossy)
Apple is planning to reset all iCloud backup data on September 22nd, 2011. As noted by 9to5Mac, the announcement was posted to Apple's developer site for both iOS and Mac developers:
On Thursday, September 22, the iCloud Backup data will be reset. Backing up to iCloud or restoring from an iCloud backup will be unavailable from 9 AM PDT – 5 PM PDT. If you attempt a backup or restore during this time, you will receive an alert that the backup or restore was not successful. After this reset, you will be unable to restore from any backup created prior to September 22. A full backup will happen automatically the next time your device backs up to iCloud.
Apple's iOS 5 has been undergoing developer testing since its announcement back in June. Developers have been able to test iCloud for backups and storage during the developer betas.
Apple has provided 7 betas to developers thus far, and had been previously rumored to be offering the Golden Master (final version before release) on September 23rd. That same rumor had also incorrectly pinpointed a Beta 8 release a few days ago, but the 23rd date seems to line up nicely with this iCloud backup reset.
Apple had said that iOS 5 would launch "this fall" which technically begins on September 23rd.
Top Rated Comments
(View all)EDIT: Now comes the interesting part: Vote down for no sense of humor, vote up for otherwise. Lets see how it goes!
Wow, 42yrs of living on Planet Earth and I never knew fall started on my birthday.
Just goes to show you never stop learning.
Or it means keynote is on 22nd with VERY short notice for invites?
I'd be suprised, but all I can say is that this will probably end being an interesting week.
I think it's a huge jump to think that a data reset implies that the release date will follow the next day, or even very shortly afterward.
A data reset suggests that Apple is changing something fundamental (e.g. the format), or otherwise fixing something that can't be done without a reset. If I were doing that, I'd want to beta test that for a while (with developers in this case), before going GM with it. The length of that test would depend on how confident I was of it being problem-free, and whether any additional problems/needed changes turn up.
Once it goes GM, the cost of a reset goes way up, both in data transfer and customer confidence. So, they would want to be very confident that they won't need to do that again, at least in the foreseeable future.
You have ruined the mood now lol