I updated the badge, it should now point to installer 3.0 for downloads. Also, I updated installer configs 4.0, 3.1 and 3.0 to point to correct version of the installer binary. This is so that the auto-update mechanism kicks in.
If no one has objections, I will go ahead and push these changes to the site live. Thanks, Om On Sat, May 3, 2014 at 12:07 AM, OmPrakash Muppirala <bigosma...@gmail.com>wrote: > I will try to find some time during the weekend to fix the badge. > > Thanks, > Om > On May 2, 2014 11:31 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> I"m done for tonight. Feel free to push the website if it is ready. >> >> -Alex >> >> On 5/2/14 11:27 PM, "Alex Harui" <aha...@adobe.com> wrote: >> >> >I updated the installer page on the web-site. It is on staging but not >> >pushed to production. >> > >> >I think we need an updated badge installer before we do more? >> > >> >Thanks, >> >-Alex >> > >> >On 5/2/14 7:26 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> > >> >>Hi, >> >> >> >>> I"m not sure we should be announcing how to get nightly builds in that >> >>> kind of public forum. >> >> >> >>I think telling people to ask on the dev list is fine (but not telling >> >>them how to do it in the announcement). We are probably going to a >> >>question or two about how to get them now that they are no longer >> visible >> >>by default. >> >> >> >>The Flex JS and Flex 4.12 SDK error rate > 50% on windows with the new >> >>installer btw, with mac it's 15% (still rather high in my option). It >> >>would be nice if we could improve that. (For FlexJS it's 117 failures/98 >> >>success on windows, for 4.12.0 47 failures/46 success on windows.) Once >> >>the new installer is out if the rate holds we be getting 100+ failures a >> >>day and we're still not 100% sure what the issue is on windows - >> >>permissions and/or AIR using IE (and not default browser) to download >> are >> >>possible candidates. >> >> >> >>Thanks, >> >>Justin >> > >> >>
