Apple now requires application developers to submit 2.2.1-oriented applications as well as build for version 3.0. I (and I guess most small / part-time developers) have only one iPhone, and since upgrading to 3.0 is irreversible, I would like to get some thoughts on what are the best methods to minimize risk during transition time.
I understand that there is no reliable way to conduct full regression testing on both operating systems, but any thoughts on how to minimize regression will be useful.
This is exactly the text of Apple:
Millions of iPhone and iPod touch customers will switch to iPhone OS 3.0 this summer. Starting today, all submissions on the App Store will be reviewed for the latest beta version of iPhone OS 3.0. If your application is not compatible with iPhone OS 3.0, it will not be approved.Existing applications in the App Store should already be running on iPhone OS 3.0 without but you should check your existing applications with iPhone OS 3.0 to make sure there are no compatibility issues. After iPhone OS 3.0 becomes available to customers, any application that is incompatible with iPhone OS 3.0 can be removed from the App Store.
Millions of iPhone and iPod touch customers will switch to iPhone OS 3.0 this summer. Starting today, all submissions on the App Store will be reviewed for the latest beta version of iPhone OS 3.0. If your application is not compatible with iPhone OS 3.0, it will not be approved.
Existing applications in the App Store should already be running on iPhone OS 3.0 without but you should check your existing applications with iPhone OS 3.0 to make sure there are no compatibility issues. After iPhone OS 3.0 becomes available to customers, any application that is incompatible with iPhone OS 3.0 can be removed from the App Store.
iPhone Dev Central, : TN2246
2.21 3.0, . , iPod Touch ( iPhone).
, 3.0 sdk 2.2.1. 2.2.1 3.0. , 2.2.1 sdk.
... . 3.0 , Apple , , .
5/17/09: , , , Mac Leopard. Apple OS X . IMHO, , , , .
2.2.1 3.0? .