Hi, > Why should we always move to a later/latest version if we don't need some > new API from some newer version? In terms of security and performance it matters. We should try and ship with the latest IMO.
> Doesn't it make the package available to more folks if we keep it running on > older versions? No we are using captive runtime. > Need more info on this. You ran the built sources and caching defaulted > to on but the folder you had previously chosen was not used? Caching was previous turned on in last version of the installer, it's disabled when I run the new version, when I enable it the new version the location is blank. Was installing 4.12.1. >> - Locale is incorrect - tried to installed china locale but logs say >> using locale is en_AU - this may cause confusion* > Has this always been the case in prior releases? Not 100% sure but don't believe so. > I thought this was desired behavior. IIRC there was a whole thread on why > the locale in flex-config should not be changed away from en_US. Can you > explain? The locale for the installer and the locale for the SDK are different - think we need to make that clear and/or add a settable locale for the SDK. Currently it confusing especially as the log shows the machine locale not the user selected locale or the SDK locale and all three locales can be different. > Are you describing an issue with the 4.13.0 install script? Was testing 4.12.1 (last release) as 4.13 has not been released yet. > Are you certain this is a bug in the installer and not in the 4.12.1 compc? Compc should report the right version - I raised this as an issue against a RC of 4.12.0 so it should of been fixed. Thanks, Justin
