Hi, > Sometimes, releases get stuck on hard issues discovered late in the game. > It is clear you want to ship as-is, but I think we should make the > third-party content look good.
I'd like to remind people that releases cannot be vetoed and votes on releases are by majority approval (ie 3+1 votes and more +1 than -1) and that releases can't be vetoed.This is to encourage small gradual improvements and frequent releases, looks like this new process effectively allows vetoing releases which would be a concern for the board. > because that’s how it will behave when published to flex.a.o. It may not. It may be a browser issue? It may be due to configuration of web server/CI windows box? For instance I'd guess that the build by the CI is not the same as the release candidate as it's using a different version of Apache Flex (ie the head of develop?) > Also, have you investigated the Squiggly issue brought up yesterday [2]? Yes I brought that issue up myself several days ago and said it doesn't occur locally. > I also get the exception. It could just be a bug in the CI server setup. As far as I can see the the ant script is using all of the correct libraries eg for spark as compiler.include-libraries includes all code the swf is they are used or not right? So that exception would be basically impossible. My local version works and a flash builder project with the same code and swc's also works. Thanks, Justin
