Re: Draft TourDeFlex announcement
Hi, We definitely want it to look good, but I would expect folks will find lots of stuff when they start poking around, so I wouldn't spend too much time on it. IMO, if a problem is found, it would be fine to modify the repo, make a local build, and drop new files on the website. Really? That would be releasing unreleased software in my books and a bit no-no under Apache rules. While we don't vote on and release the web site content but this content come from releasable software and is code so I really don't think we can do that. It's really not too hard to call a vote on this, and it's relatively easy to compile and test, lets actually try and follow the Apache Way here. Small gradual improvement and release as often as we can. And/Or, if you want to be really bold, we could set up Jenkins to deploy a nightly build to the site. --1 to that, procedure aside, we don't want to be publishing potentially very broken stuff to the web site. And given the number of times Jenkins seems to stuff up, it seem very risky to me. Thanks, Justin
Re: Git merge issue in Flex utilities
Hi, Agreed, and so, lesson learned: this is why we do need to cut release branches even if there isn't much going on in develop branch. Or would the release branch also contain these blazeDS and the merge would have tired to merge them? A release branch would of been of little help here. The issue is that we have several projects in a git repo each under their own directory and git prefers one project per repo. Justin
Re: Draft TourDeFlex announcement
On 8/22/14 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, We definitely want it to look good, but I would expect folks will find lots of stuff when they start poking around, so I wouldn't spend too much time on it. IMO, if a problem is found, it would be fine to modify the repo, make a local build, and drop new files on the website. Really? That would be releasing unreleased software in my books and a bit no-no under Apache rules. While we don't vote on and release the web site content but this content come from releasable software and is code so I really don't think we can do that. Might be a good question for general@incubator. Mind if I ask there? It's an interesting case. If we were to put any other app on flex.a.o, we wouldn't be making source code available for the general public, but I suppose one could argue that with TDF, at least the example source is being made available, although not as a package. It's really not too hard to call a vote on this, and it's relatively easy to compile and test, lets actually try and follow the Apache Way here. Small gradual improvement and release as often as we can. I'm all for faster release cycles. I think it is 30 minutes minimum to validate the TDF RC. Given the potentially high traffic and profile TDF might get, we might be tempted to immediately fix any problem reported. Doing daily releases would be a little too fast for me. And/Or, if you want to be really bold, we could set up Jenkins to deploy a nightly build to the site. --1 to that, procedure aside, we don't want to be publishing potentially very broken stuff to the web site. And given the number of times Jenkins seems to stuff up, it seem very risky to me. Only successful builds would get pushed. Anyway, we'll see what others think. -Alex
Re: Git merge issue in Flex utilities
On 8/22/14 11:15 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Agreed, and so, lesson learned: this is why we do need to cut release branches even if there isn't much going on in develop branch. Or would the release branch also contain these blazeDS and the merge would have tired to merge them? A release branch would of been of little help here. The issue is that we have several projects in a git repo each under their own directory and git prefers one project per repo. Should we ask for more repos? Or maybe just one where new donations go until released? -Alex
Re: Draft TourDeFlex announcement
Hi, Might be a good question for general@incubator. Mind if I ask there? Ask away. But I think we should set a good example here and not try and get around the rules. I'm all for faster release cycles. I think it is 30 minutes minimum to validate the TDF RC. It not really that complex to validate it IMO. And if we release often there well be less changes between versions and as it really multiple small applications you have a good idea of which ones you need to look at and which you can ignore. Given the potentially high traffic and profile TDF might get, we might be tempted to immediately fix any problem reported. There is no need to fix every issue immediately, we just need to acknowledge the issue (like in JIRA for instance), hopefully someone will fix it, and it can be released when we make the next release. Exactly the same situation as the SDK, it's not like that is 100% bug free (or we would have no open JIRAs) Doing daily releases would be a little too fast for me. I don't think we need daily releases and voting periods will overlap probably making it very confusing. But if enough people show interest and contribute examples I could see a release a month. Only successful builds would get pushed. Which can still be non functioning, should we ship everything just because it compiles? Thanks, Justin
Re: Draft TourDeFlex announcement
We had a big discussion about this when we released the first version of the Installer badge, installer config xml, etc. which goes on the website as well. You both might want to refresh on that thread before taking it to general@i.a.o. In the meantime, I have couple of spare hours tonight and I want to make it productive. I am going to go with the RC3 bits to avoid any further arguments. Thanks, Om On Fri, Aug 22, 2014 at 11:47 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Might be a good question for general@incubator. Mind if I ask there? Ask away. But I think we should set a good example here and not try and get around the rules. I'm all for faster release cycles. I think it is 30 minutes minimum to validate the TDF RC. It not really that complex to validate it IMO. And if we release often there well be less changes between versions and as it really multiple small applications you have a good idea of which ones you need to look at and which you can ignore. Given the potentially high traffic and profile TDF might get, we might be tempted to immediately fix any problem reported. There is no need to fix every issue immediately, we just need to acknowledge the issue (like in JIRA for instance), hopefully someone will fix it, and it can be released when we make the next release. Exactly the same situation as the SDK, it's not like that is 100% bug free (or we would have no open JIRAs) Doing daily releases would be a little too fast for me. I don't think we need daily releases and voting periods will overlap probably making it very confusing. But if enough people show interest and contribute examples I could see a release a month. Only successful builds would get pushed. Which can still be non functioning, should we ship everything just because it compiles? Thanks, Justin
Falcon build generating maven artifacts
Hi, so I just committed my changes to the build.xml and download.xml. the current version in the dev branch now has a maven-artifact target that additionally installs some jars to your local maven repo after finishing the build. Unfortunateley I couldn't fix the other issue I reported yesterday as downloads.sourceforge.net is completely unresponsive and I'm currently unable to build anymore (I did a wipe to re-test everything and after that I couldn't build again). Guess this is exactly what I meant by depending on several other sites for downloads. One other thing I noticed. The Readme in falcon states you need to set the JFLEX_JAR?, but that is not quite correct and I remember having to set something like FLEX_HOME etc. Eventually someone should revamp that file. I would have done that, but I'm not so sure if I know all that would have to go in there. Chris
Re: Draft TourDeFlex announcement
Hi, In the meantime, I have couple of spare hours tonight and I want to make it productive. I am going to go with the RC3 bits The RC3 bits and the tag are both identical so either is fine. If you run into any issue post here I'm up or 5 or 6 hours yet. Thanks, Justin
AW: Build failed in Jenkins: flex-falcon #143
Actually I didn't break it ... it's just that downloads.sourceforge.net is currently not available, which is causing the build to fail ... so no need for high blood pressure ... all will be good in a few ... oh whatever the sourceforge speed-unit is ;-) Chris -Ursprüngliche Nachricht- Von: flex.ci.bui...@gmail.com [mailto:flex.ci.bui...@gmail.com] Gesendet: Samstag, 23. August 2014 10:00 An: comm...@flex.apache.org; Christofer Dutz; e...@ixsoftware.nl; bigosma...@gmail.com; aha...@adobe.com Betreff: Build failed in Jenkins: flex-falcon #143 See http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/143/changes Changes: [christofer.dutz] Implemented maven artifact generation. -- Started by an SCM change Building remotely on flex_sdk_slave2 in workspace http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/ No JDK named ‘(Default)’ found Fetching changes from the remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-falcon.git Checking out Revision 30139d0fc00d004d33e763a97f58e75293498c09 (origin/develop) No JDK named ‘(Default)’ found [flex-falcon] $ cmd.exe /C 'c:\Jenkins\tools\hudson.tasks.Ant_AntInstallation\c_apache-ant-1.9.3\bin\ant.bat -file jenkins.xml main exit %%ERRORLEVEL%%' Buildfile: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins.xml clean: [delete] Deleting directory http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/temp [delete] Deleting directory http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/JFlex [delete] Deleting directory C:\Google\Closure\Library init: [mkdir] Created dir: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/temp [mkdir] Created dir: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/JFlex [mkdir] Created dir: C:\Google\Closure\Library jflex-download: [echo] Be patient. This takes a few minutes... [get] Getting: http://jflex.de/jflex-1.4.3.zip [get] To: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/temp/JFlex.zip [unzip] Expanding: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/temp/JFlex.zip into http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/jenkins/JFlex closure-lib-download: [echo] Be patient. This takes a few minutes... [exec] Cloning into 'C:\Google\Closure\Library'... [exec] Checking out files: 36% (856/2318) [exec] Checking out files: 37% (858/2318) Checking out files: 38% (881/2318) Checking out files: 39% (905/2318) Checking out files: 40% (928/2318) Checking out files: 41% (951/2318) Checking out files: 42% (974/2318) Checking out files: 43% (997/2318) Checking out files: 44% (1020/2318) Checking out files: 45% (1044/2318) Checking out files: 45% (1066/2318) Checking out files: 46% (1067/2318) Checking out files: 47% (1090/2318) Checking out files: 48% (1113/2318) Checking out files: 49% (1136/2318) Checking out files: 50% (1159/2318) Checking out files: 51% (1183/2318) Checking out files: 52% (1206/2318) Checking out files: 53% (1229/2318) Checking out files: 54% (1252/2318) Checking out files: 55% (1275/2318) Checking out files: 56% (1299/2318) Checking out files: 57% (1322/2318) Checking out files: 58% (1345/2318) Checking out files: 59% (1368/2318) Checking out files: 60% (1391/2318) Checking out files: 61% (1414/2318) Checking out files: 62% (1438/2318) Checking out files: 63% (1461/2318) Checking out files: 64% (1484/2318) Checking out files: 65% (1507/2318) Checking out files: 66% (1530/2318) Checking out files: 67% (1554/2318) Checking out files: 68% (1577/2318) Checking out files: 69% (1600/2318) Checking out files: 70% (1623/2318) Checking out files: 71% (1646/2318) Checking out files: 72% (1669/2318) Checking out files: 73% (1693/2318) Checking out files: 74% (1716/2318) Checking out files: 75% (1739/2318) Checking out files: 76% (1762/2318) Checking out files: 77% (1785/2318) Checking out files: 78% (1809/2318) Checking out files: 79% (1832/2318) Checking out files: 79% (1842/2318) Checking out files: 80% (1855/2318) Checking out files: 81% (1878/2318) Checking out files: 82% (1901/2318) Checking out files: 83% (1924/2318) Checking out files: 84% (1948/2318) Checking out files: 85% (1971/2318) Checking out files: 86% (1994/2318) Checking out files: 87% (2017/2318) Checking out files: 88% (2040/2318) Checking out files: 89% (2064/2318) Checking out files: 90% (2087/2318) Checking out files: 90% (2094/2318) Checking out files: 91% (2110/2318) Checking out files: 92% (2133/2318) Checking out files: 93% (2156/2318) Checking out files: 94% (2179/2318) Checking out files: 95% (2203/2318) Checking out
Re: Draft TourDeFlex announcement
Okay, it has been pushed into the staging area. You can test it by going to http://flex.staging.apache.org and selecting About Flex Tour de Flex Or directly go to the page: http://flex.staging.apache.org/tourdeflex/explorer.html I will check tomorrow morning for any feedback. If none, I will go ahead and push it to production. Thanks, Om On Sat, Aug 23, 2014 at 12:59 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, In the meantime, I have couple of spare hours tonight and I want to make it productive. I am going to go with the RC3 bits The RC3 bits and the tag are both identical so either is fine. If you run into any issue post here I'm up or 5 or 6 hours yet. Thanks, Justin
Re: Draft TourDeFlex announcement
Hi, Or directly go to the page: http://flex.staging.apache.org/tourdeflex/explorer.html I will check tomorrow morning for any feedback. If none, I will go ahead and push it to production. Looks good to me. One minor issue we probably need to change where the loading bar is located which is not noticeable when running locally. Someone mind raising a JIRA? Justin
RE: Falcon build generating maven artifacts
The Readme in falcon states you need to set the JFLEX_JAR?, but that is not quite correct Good to know I did it for nothing :-) will try without at some point this week. Frédéric THOMAS From: christofer.d...@c-ware.de To: dev@flex.apache.org Subject: Falcon build generating maven artifacts Date: Sat, 23 Aug 2014 07:40:54 + Hi, so I just committed my changes to the build.xml and download.xml. the current version in the dev branch now has a maven-artifact target that additionally installs some jars to your local maven repo after finishing the build. Unfortunateley I couldn't fix the other issue I reported yesterday as downloads.sourceforge.net is completely unresponsive and I'm currently unable to build anymore (I did a wipe to re-test everything and after that I couldn't build again). Guess this is exactly what I meant by depending on several other sites for downloads. One other thing I noticed. The Readme in falcon states you need to set the JFLEX_JAR?, but that is not quite correct and I remember having to set something like FLEX_HOME etc. Eventually someone should revamp that file. I would have done that, but I'm not so sure if I know all that would have to go in there. Chris
RE: Git merge issue in Flex utilities
There are many things now in this repo, couldn't itbe useful to split it up into pieces, especially for the Installer and blazeDS ? Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Git merge issue in Flex utilities Date: Sat, 23 Aug 2014 06:38:35 + On 8/22/14 11:15 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Agreed, and so, lesson learned: this is why we do need to cut release branches even if there isn't much going on in develop branch. Or would the release branch also contain these blazeDS and the merge would have tired to merge them? A release branch would of been of little help here. The issue is that we have several projects in a git repo each under their own directory and git prefers one project per repo. Should we ask for more repos? Or maybe just one where new donations go until released? -Alex
RE: Git merge issue in Flex utilities
Sorry, I meant TDF :-) Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Git merge issue in Flex utilities Date: Sat, 23 Aug 2014 12:28:58 +0100 There are many things now in this repo, couldn't itbe useful to split it up into pieces, especially for the Installer and blazeDS ? Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Git merge issue in Flex utilities Date: Sat, 23 Aug 2014 06:38:35 + On 8/22/14 11:15 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Agreed, and so, lesson learned: this is why we do need to cut release branches even if there isn't much going on in develop branch. Or would the release branch also contain these blazeDS and the merge would have tired to merge them? A release branch would of been of little help here. The issue is that we have several projects in a git repo each under their own directory and git prefers one project per repo. Should we ask for more repos? Or maybe just one where new donations go until released? -Alex
Re: Draft TourDeFlex announcement
Can the page have a favicon? The tab is showing up with a blank rectangle beside its name rather than an image in Chrome. On Sat, Aug 23, 2014 at 8:11 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Or directly go to the page: http://flex.staging.apache.org/tourdeflex/explorer.html I will check tomorrow morning for any feedback. If none, I will go ahead and push it to production. Looks good to me. One minor issue we probably need to change where the loading bar is located which is not noticeable when running locally. Someone mind raising a JIRA? Justin -- Andrew Wetmore http://cottage14.blogspot.com/ http://portfolio.cottage14.com http://annapolisndp.ca
Re: Draft TourDeFlex announcement
Hi, I checked http://flex.staging.apache.org/tourdeflex/explorer.html and it looks that skins from examples are missing? Like in example for Button Width Icon, I expected to see skin's files in tabs. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Draft-TourDeFlex-announcement-tp39916p39949.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Draft TourDeFlex announcement
Hi, Can the page have a favicon? Thanks for checking it out I've raised a JIRA for the misisng favicon here [1] Justin 1. https://issues.apache.org/jira/browse/FLEX-34488
Re: Draft TourDeFlex announcement
Hi, I checked http://flex.staging.apache.org/tourdeflex/explorer.html and it looks that skins from examples are missing? Like in example for Button Width Icon, I expected to see skin's files in tabs. Nice feedback. Looks like a couple of examples are not showing all of the files they should in the tabs. I've raised a JIRA here. [1] Thanks, Justin 1. https://issues.apache.org/jira/browse/FLEX-34489
AW: Draft TourDeFlex announcement
Well I did find two things: - The Spark Video example produces a Playback Error - The Spark Module Load example just shows up the module panel for fragments of a second and then disapears again. Chris -Ursprüngliche Nachricht- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Samstag, 23. August 2014 15:20 An: dev@flex.apache.org Betreff: Re: Draft TourDeFlex announcement Hi, I checked http://flex.staging.apache.org/tourdeflex/explorer.html and it looks that skins from examples are missing? Like in example for Button Width Icon, I expected to see skin's files in tabs. Nice feedback. Looks like a couple of examples are not showing all of the files they should in the tabs. I've raised a JIRA here. [1] Thanks, Justin 1. https://issues.apache.org/jira/browse/FLEX-34489
Re: Draft TourDeFlex announcement
I should have said earlier that I am delighted the Tour is back. One of my favorite tools both in my own development work and for showing others what Flex and do and how easily it can do it. On Sat, Aug 23, 2014 at 10:45 AM, Christofer Dutz christofer.d...@c-ware.de wrote: Well I did find two things: - The Spark Video example produces a Playback Error - The Spark Module Load example just shows up the module panel for fragments of a second and then disapears again. Chris -Ursprüngliche Nachricht- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Samstag, 23. August 2014 15:20 An: dev@flex.apache.org Betreff: Re: Draft TourDeFlex announcement Hi, I checked http://flex.staging.apache.org/tourdeflex/explorer.html and it looks that skins from examples are missing? Like in example for Button Width Icon, I expected to see skin's files in tabs. Nice feedback. Looks like a couple of examples are not showing all of the files they should in the tabs. I've raised a JIRA here. [1] Thanks, Justin 1. https://issues.apache.org/jira/browse/FLEX-34489 -- Andrew Wetmore http://cottage14.blogspot.com/ http://portfolio.cottage14.com http://annapolisndp.ca
Re: Draft TourDeFlex announcement
Hi, - The Spark Video example produces a Playback Error - The Spark Module Load example just shows up the module panel for fragments of a second and then disapears again. Mind raising JIRA's for these? Justin
Re: Draft TourDeFlex announcement
Hi, I should have said earlier that I am delighted the Tour is back. One of my favorite tools both in my own development work and for showing others what Flex and do and how easily it can do it. Nice to hear. Now even better you can improve and add to the examples. Thanks, Justin
RE: FlexUnit Training on website and Flash Builder 4.7
Started to think about updating the tutorial to also walk them through the UI differences too. Before I get too far into this, I wanted to run it past the team. Is it cool if I go ahead and update the tutorials to also include the variations in FB 4.7 versus FB 4.6? I don't have time to work with you on this but I am willing to be a resource in _any_ way I can help. Any questions, comments or conversations you want to have, I will make time to address. If there are things we can plan to fix to make anything smoother I can at least help get the Jira issues in or point someone in the right direction. As of late, I have been a bit overwhelmed with client work but if there are ways I can help you be more successful, please let me know and I will find a way. Thanks for working on this, Mike
Re: Git merge issue in Flex utilities
Only if the release branches didn't bring over other changes too. Unlike some of our other repo's this one has many balls in the air at a time. -Mark On Sat, Aug 23, 2014 at 1:25 AM, Alex Harui aha...@adobe.com wrote: On 8/22/14 9:47 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I think for already released products, master should only get updated with a released copy. But it is a good question about whether the donations should have been dropped into master as the master copy of the ip-cleared donation, even if they weren't ready to go. So that's why I'm ok with you merging the whole thing. Fair enough done - this is going to get tricky in the future however. And there will be some stuff that probably strictly shouldn't be in master ie mavinizer and blaze DS unreleased changes. Agreed, and so, lesson learned: this is why we do need to cut release branches even if there isn't much going on in develop branch. Or would the release branch also contain these blazeDS and the merge would have tired to merge them? Or does a merge only apply diffs from the branch point so it would work? And also, motivation to release those yet-to-be-released entities. I saw Chris mention he might try to do BlazeDS -Alex
Re: Draft TourDeFlex announcement
Hi, New draft, any other issues on the staging site or content changes below required before we announce the release? After the staging content is made live first of course. Thanks, Justin - The Apache Flex community is pleased to announce the release of Apache Flex TourDeFlex 1.0 The Apache Flex Tour De Flex component explorer provides a sample set of working Apache Flex examples. This application is based on work donated by Adobe and their component explorer and is expected to be updated over time. We welcome feedback and contributions to it from the widerApache Flex community. The Apache Flex TourDeFlex is available in source form for you to compile from the following download page: http://www.apache.org/dyn/closer.cgi/flex/tourdeflex/1.0 When downloading from a mirror site, please remember to verify the downloads using signatures or MD5 hashes. For your convenience have it has been compiled and placed upon on the Apache Flex web site: http://flex.apache.org/tourdeflex/explorer.html For more information on Apache Flex, visit the project home page: http://flex.apache.org http://flex.apache.org/ http://flex.apache.org/ Thank you for using Apache Flex, The Apache Flex Community -
Re: Draft TourDeFlex announcement
Hi, Raised JIRAs for these issues. - The Spark Video example produces a Playback Error https://issues.apache.org/jira/browse/FLEX-34490 - The Spark Module Load example just shows up the module panel for fragments of a second and then disapears again. https://issues.apache.org/jira/browse/FLEX-34491 Thanks again for finding them. Justin
