>Please try it yourself. Ok, but I couldn't find in this thread a detaild description of the issue. Could you please point me to the exact mail, and if none, describe what needs to be tested.
> I have to defer to the non-en_US folks on these matters. One question: do > all of your projects set the locale chain explicitly? If so, >then I think > this issue does not affect you. I think it will only affect you if you have > projects that do not have locales for your country that you built >relying on > the default SDK locale being set to en_US. Erik, for example, is doing work > for a US-based company and may get caught building some >library if it only > has en_US resources and does not explicitly set en_US in the build script or > project properties. Usually, we set en_US as a fallback locale on all our projects compiler options, along with the other supported locales (en_GB, fr_FR, es_SP, etc...). The localChain is then dynamically set from some external settings (typically, Browser or system locale). If the locale is not found, we simply fall back to en_US. So if I understand you, my projects won't be affected. Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : dimanche 16 mars 2014 15:42 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC7 On 3/16/14 2:53 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >IIUC, installer 3.0 is good enough, but the installer.xml file in the >4.12 release SDK is not good. > >So IMO, we shouldn't make a release now, because in this case, >installer >3.0 will replace 2.7 as the default installer page (installer.html). > >So people who install Flex using the official combination of installer >+ SDK 4.12 will get an error, right? Please try it yourself. I have to defer to the non-en_US folks on these matters. One question: do all of your projects set the locale chain explicitly? If so, then I think this issue does not affect you. I think it will only affect you if you have projects that do not have locales for your country that you built relying on the default SDK locale being set to en_US. Erik, for example, is doing work for a US-based company and may get caught building some library if it only has en_US resources and does not explicitly set en_US in the build script or project properties. > >I think we should wait until the next point release (SDK 4.12.1) to >make an official release of the installer. I would have preferred a request to delay announcing/switching to Installer 3.0 vs voting -1. We delayed the announcement of 4.12 to try to wait for the Installer. I think we can consider 3.0 done and wait to announce and force the auto-upgrade until 4.12.1 is finished. Then I can go work on other things in the interim. How does that plan sound to everyone? -Alex
