On May 19, 2014 11:59 PM, "Alex Harui" <aha...@adobe.com> wrote: > > > > On 5/19/14 11:35 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > >On May 19, 2014 11:28 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> > >> I believe we don't know if the failure rate is lower with 2.7. It could > >> simply be the same, especially if folks are getting as far as antlr, > >>gcc, > >> or some other third-party download before it fails. > > > >I meant bringing the old Installer back for the Flex SDK installation and > >using the new Installer for FlexJS. Until we sort this out. > How would that work? If someone gets 3.0 for FlexJS, they will end up > using it for 4.12.2 unless they remember to downgrade? > > And again, it isn't clear to me that 2.7 doesn't have the same problems, > it is just that failures are not reported in 2.7.
You are right. We may be having the same error rate with 2.7 and we just don't know it. > > > >I can add the console log tracking right away if you are okay with > >releasing that as 3.0.1. Works? > Any concerns the log gets too long or is too different so it is hard to > track? I was going to try to add some status string to send. Should be no problems with sending a long string. > > I'm wondering if we should rush this out or try to tackle some of the > known issues that were reported like the streaming error and bad > downloads. Let's see what others say. > I would rather push a release now with more failure tracking info than wait. Anyone else, any thoughts? Thanks, Om > Thanks, > -Alex >
