On 2/2/15, 7:40 AM, "Tom Chiverton" <[email protected]> wrote:
>On 02/02/15 15:25, Alex Harui wrote: >> IIRC, 11.1 is the only/latest version for which Adobe has promised >>support >> for Flex. Also, IIRC, some customers don’t like being forced to go to >>the >> latest. >> >> That doesn’t mean we shouldn’t switch, but just more data for you to >> consider. >> > >I read the "Adobe runtime support of Flex" section on >http://www.adobe.com/devnet/flex/whitepapers/roadmap.html >and it says (to my mind) that Adobe doesn't support any version of >Apache Flex on any version of Player... Well, you are right that there isn’t an explicit promise, but this part: "Flash Player 11.2 and Adobe AIR 3.2, which are anticipated to ship in the first quarter of 2012, will be tested with applications built using Adobe Flex 4.6. Adobe will test future releases of Flash Player and AIR against the Adobe Flex 4.6 SDK and maintain backwards compatibility for five years.” (although I notice it does say 11.2 instead of 11.1 which was the latest we had at the time of the transition) means to me that Adobe is going to verify that SWFs built with whatever SWF version is the default for 11.2 will continue to run in the new players. New code paths can be added to the new player for other SWF versions that may break Apache Flex or Adobe Flex apps, although we have yet to find any, and IIRC, Adobe would break old SWFs in order to solve a really serious security issue. Thinking about this more, though, the only things the player version in the SDK repo affects is what APIs are available at compile time to the CI server unless we set some option for a different player version in the CI server setup, and what the default is for the minority that use the source package. So if we upgrade, we run the risk of using a new player API that doesn’t work on older players. But for the vast majority of folks who use the Installer or installer.xml it doesn’t matter. -Alex
