On 7/31/13 4:34 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> I would like the release to contain the IList revert, the resource >>modules >> fix, and the ProductInfo change to "Apache Flex". >Is there any advance on that? Not sure what you mean. But it is all checked into the release and develop branches. > >> The version can remain at 4.10.0. >Even though this will mean that "New Project" in both Flash builder 4.6 >and 4.7 are broken? At some future point Adobe may release an update to >4.7 to fix this, but until then it will be an issue. Just want to be >clear here as strong objections were raised about this. That's my position. Let's see what others say, but that's what I thought the consensus was from the other thread. > >> I think the README is ok, >The README is not up to date re JIRA or AIR versions I think. OK, can you take care of that? > >> How about I add a "Known Issues" section to RELEASE_NOTES >+1 > >> that points to a new page on our wiki so we can update wiki as needed? >While useful it sound like just avoiding making releases to me. Know >issues should be in the RELASE_NOTES at the time of release. If any new >issues come up then we should make a new point release to fix. Sorry, I wasn't clear. The Known Issues section in the readme would contain a description of the "new project" problem and tell folks to look on the wiki for the latest on that problem only. That's the only known issue I know of, but if there were others I agree they would be in the RELEASE_NOTES as you are suggesting. I'm about to commit the wiki page and RELEASE_NOTES. Yelp if you don't like it. > >Thanks, >Justin
