We are supposed to cut RCs from the release branch. Folks are supposed to make last minute changes to the release branch. It is risky to merge from develop into a release branch, so it would be better if the folks who made commits to develop determine if they want their changes to go out in this release and revert from develop and commit to release. Or study the logs and make sure nothing else got committed to develop that shouldn't go in release and do the merge.
Peter and I are still chasing down bugs in the examples. I don't imagine cutting before the end of Friday, and it would require folks like you to say that they've examined the bits and they are ready. So far, only Josh has given a thumbs up. I took my thumb back down after Yishay found all of those problems with FB integration and I started seeing issues in the examples. Thanks, -Alex On 5/18/17, 8:12 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Hi Alex, > >There are couple of minor commits in develop - In what state is this >branch >? I don't see any problems with merging them to release, but maybe I don't >have enough knowledge. Do you expect something in those branch or are you >going to cut release ? > >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FLAST-CALL-Release-FlexJS-FalconJX-0- >8-0-tp61275p61688.html&data=02%7C01%7C%7C4355f3d21cc64ba8e17808d49e66b2fa% >7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636307611309291129&sdata=mjJ% >2BHR2dX1hC17tyij7r93PT4BiyLqw2qx5pX9ocLNs%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
