Re: [VOTE] Apache FlexJS 0.0.1 RC3
+1 (binding) - sigs OK - docs meagre but OK - source builds - DataBindingTest good for both SWF and JS Alpha, but already excellent! EdB On Mon, Apr 21, 2014 at 2:43 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, +1 (binding) NOTICE, LICENCE, RELEASE_NOTE all OK (very minor formatting/line length issues) checksum/sigs good rat report OK (frameworks/js/jshint.properties is missing header) no binaries in source (except images) can compile from source unit tests pass - although coverage is currently poor (eg one flex unit test testing setting a column label) Note if this wasn't an alpha I wouldn't vote +1 - documentation/setup instructions needs some work need eg list all dependancies and versions needed eg python, node etc etc - no list of known issues - poor test coverage - unclear which examples are working - ant in some examples directory fail Tested on OSX. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Build Servers
Let's not make every discussion on this list about bylaws and regulations. If I find time, I'll build the VM and finally get the CI nightmare that Apache itself provides behind me. If the lawyers decide that the Apache servers are better than the VM (lol) then we won't serve nightlies from the VM, but create a lone job on 'builds@a.o' and hope they manage to keep it running well enough to produce a nightly every week or so. EdB On Mon, Apr 21, 2014 at 12:46 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, Are we sure it''s OK to serve nightlies off non ASF machines? May want to confirm before putting time and effort into this. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Build Servers
OK, will ask. I'll be highly surprised if it an issue. I think if it were up to Roy there wouldn't be any builds.a.o. -Alex On 4/20/14 3:46 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Are we sure it''s OK to serve nightlies off non ASF machines? May want to confirm before putting time and effort into this. Justin
Re: Build Servers
Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: 4.12.1
I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218
AW: Build Servers
Hi, on the ApacheCon we were told that it is possible for any Apache Project to get a dedicated VM ... perhaps this would be something we should use? And it would be definitely possible to setup a build agent on that VM and have Infra set that up in the public Jenkins (That agent would be flagged with ApacheFlex or something like that and our builds would be flagged with needs ApacheFlex. Then we would be using the public CI server but be running on our own Agents. Think that's a sensible solution. I even mentioned the option to Add external Agents, this would be possible, but Infra would prefer Apache Internal VMs in order to avoid any unwanted Influence of external parties (Namely a company sponsoring a vm and using that to influence votes ... well I guess it was a little paranoid, but a valid thought) Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Montag, 21. April 2014 08:22 An: dev@flex.apache.org Betreff: Re: Build Servers Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and +that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: Build Servers
I don't know if you can Sysprep a virtual OS your remoting into... -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Sunday, April 20, 2014 2:46 PM To: dev@flex.apache.org Subject: Re: Build Servers On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: Latest News not updated
I believe the bot which puts the site content together is not functioning ATM. But there is content waiting in the staging area. I'm sure when the bot is working again it will update itself. -Mark -Original Message- From: Rushme Nayak [mailto:rushme.nay...@gmail.com] Sent: Monday, April 21, 2014 12:49 AM To: dev@flex.apache.org Subject: Latest News not updated In https://flex.apache.org/ *Latest news* section is not updated to show Apache FlexUnit release. -- Warm Regards, *Rush-me*
RE:4.12.1
Yes, I did the fix but not committed yet, as I want to fix the GC issue as well De : Alex Harui [aha...@adobe.com] Envoyé : lundi 21 avril 2014 09:02 À : dev@flex.apache.org Objet : Re: 4.12.1 I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218
Re: Latest News not updated
The Apache CMS is currently down (and has been since Wednesday), so the updates we've made to the website are not live. They should (hopefully) be updated sometime today. -Nick On Mon, Apr 21, 2014 at 5:59 AM, mark.kessler@usmc.mil wrote: I believe the bot which puts the site content together is not functioning ATM. But there is content waiting in the staging area. I'm sure when the bot is working again it will update itself. -Mark -Original Message- From: Rushme Nayak [mailto:rushme.nay...@gmail.com] Sent: Monday, April 21, 2014 12:49 AM To: dev@flex.apache.org Subject: Latest News not updated In https://flex.apache.org/ *Latest news* section is not updated to show Apache FlexUnit release. -- Warm Regards, *Rush-me*
Re: Build Servers
Chris, I read and understood your previous emails on this subject. It all sounds awesome, and I'm sure the infra folks you talked to at the time meant what they said. But in my experience, what infra says and what they actually do (within a reasonable timeframe) are two entirely different things. I've spend way too much time this past year trying to work with them to keep the one VM up and running for more than a week. They just can't manage even that. In addition, they have (up till a week ago) denied all offers to help them. So, I'm done with them. If someone else has the cycles to keep fighting the windmills, they are welcome to it. I'm going to help set up our own, external VM. After that, I'm going back to actually writing code for the project. There are compilers out there that need some love ;-) Thanks, EdB On Monday, April 21, 2014, Christofer Dutz christofer.d...@c-ware.de wrote: Hi, on the ApacheCon we were told that it is possible for any Apache Project to get a dedicated VM ... perhaps this would be something we should use? And it would be definitely possible to setup a build agent on that VM and have Infra set that up in the public Jenkins (That agent would be flagged with ApacheFlex or something like that and our builds would be flagged with needs ApacheFlex. Then we would be using the public CI server but be running on our own Agents. Think that's a sensible solution. I even mentioned the option to Add external Agents, this would be possible, but Infra would prefer Apache Internal VMs in order to avoid any unwanted Influence of external parties (Namely a company sponsoring a vm and using that to influence votes ... well I guess it was a little paranoid, but a valid thought) Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com javascript:;] Gesendet: Montag, 21. April 2014 08:22 An: dev@flex.apache.org javascript:; Betreff: Re: Build Servers Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official +that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I.
Re: 4.12.1
https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
Re: 4.12.1
Maurice, are you going to look at this again or do you need someone else to take it? -ALex On 4/21/14 5:46 AM, Lee Burrows subscripti...@leeburrows.com wrote: https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
Re: Build Servers
I think we should ask Infra for an Azure VM. We need to prove clone-ability of whatever we build up on my VM. And it wouldn't hurt to have another build machine that runs a different player config. And if it turns out we can run that VM at a higher speed we might clone some of the mustella testing to it as well. If there are no objections over the next day or two I will try to figure out what we need to do to get one. -Alex On 4/21/14 5:02 AM, Erik de Bruin e...@ixsoftware.nl wrote: Chris, I read and understood your previous emails on this subject. It all sounds awesome, and I'm sure the infra folks you talked to at the time meant what they said. But in my experience, what infra says and what they actually do (within a reasonable timeframe) are two entirely different things. I've spend way too much time this past year trying to work with them to keep the one VM up and running for more than a week. They just can't manage even that. In addition, they have (up till a week ago) denied all offers to help them. So, I'm done with them. If someone else has the cycles to keep fighting the windmills, they are welcome to it. I'm going to help set up our own, external VM. After that, I'm going back to actually writing code for the project. There are compilers out there that need some love ;-) Thanks, EdB On Monday, April 21, 2014, Christofer Dutz christofer.d...@c-ware.de wrote: Hi, on the ApacheCon we were told that it is possible for any Apache Project to get a dedicated VM ... perhaps this would be something we should use? And it would be definitely possible to setup a build agent on that VM and have Infra set that up in the public Jenkins (That agent would be flagged with ApacheFlex or something like that and our builds would be flagged with needs ApacheFlex. Then we would be using the public CI server but be running on our own Agents. Think that's a sensible solution. I even mentioned the option to Add external Agents, this would be possible, but Infra would prefer Apache Internal VMs in order to avoid any unwanted Influence of external parties (Namely a company sponsoring a vm and using that to influence votes ... well I guess it was a little paranoid, but a valid thought) Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com javascript:;] Gesendet: Montag, 21. April 2014 08:22 An: dev@flex.apache.org javascript:; Betreff: Re: Build Servers Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean
Re: [VOTE] Accept Adobe Donation
+1 (binding) On 4/17/14 3:32 PM, Alex Harui aha...@adobe.com wrote: Please vote to accept the donation of the following Flex-related code and documentation from Adobe Systems, Inc. The vote will be open for at least 72 hours. Thanks, -Alex In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbui l der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex. h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklis t .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tri c ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html FlexPMD is currently on Open@Adobe here: http://sourceforge.net/adobe/flexpmd/home/Home/ The Mobile Trader demo application is described here: http://www.adobe.com/devnet/flex/samples/mobile-trader-application.html And here: http://coenraets.org/blog/2011/03/flex-on-the-ipad/ The XML merge utility is a small set of files that should have been in the BlazeDS donation Squiggly is described here: http://labs.adobe.com/technologies/squiggly/ Tour De Flex is described here: http://www.adobe.com/devnet/flex/tourdeflex.html
[RESULT][VOTE] Accept Adobe Donation
Vote passed with 11 +1 (binding) votes, no 0 and no -1 votes. The community also pitched in with 7 +1 votes, no 0 votes and no -1 votes. Next step: IP Clearance from the Incubator. Thanks, -Alex On 4/17/14 3:32 PM, Alex Harui aha...@adobe.com wrote: Please vote to accept the donation of the following Flex-related code and documentation from Adobe Systems, Inc. The vote will be open for at least 72 hours. Thanks, -Alex In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbui l der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex. h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklis t .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tri c ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html FlexPMD is currently on Open@Adobe here: http://sourceforge.net/adobe/flexpmd/home/Home/ The Mobile Trader demo application is described here: http://www.adobe.com/devnet/flex/samples/mobile-trader-application.html And here: http://coenraets.org/blog/2011/03/flex-on-the-ipad/ The XML merge utility is a small set of files that should have been in the BlazeDS donation Squiggly is described here: http://labs.adobe.com/technologies/squiggly/ Tour De Flex is described here: http://www.adobe.com/devnet/flex/tourdeflex.html
Re: [VOTE] Apache FlexJS 0.0.1 RC3
+1 (Binding) Peter Ent Adobe Systems On 4/19/14 2:10 AM, Alex Harui aha...@adobe.com wrote: Hi, This is vote for the initial (0.0.1) release of Apache FlexJS. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/flex/flexjs/0.0.1/rc3/ Before voting please review the section,What are the ASF requirements on approving a release?, at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - MD5 and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - As this is the first release please carefully check the LICENSE and NOTICE files - That the build script completes successfully - That you can compile and cross-compile a simple example using the SDK. The source package is set up the same way as the repo. This means that the results of the build are not the same as an IDE-compatible SDK. The compiled source package can be used in combination with the FalconJX source package to compile some of the sample applications. The most convenient way to use the binary package is to install it via Ant or the Installer. To use an Installer you must use InstallApacheFlex version 3.0 or later which is still in release candidate status at this time. You can get InstallApacheFlex 3.0 here: https://dist.apache.org/repos/dist/dev/flex/installer/3.0/rc7/binaries/ Please vote to approve this release: +1 Approve the release -1 Veto the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is an initial 'alpha-quality' release so I expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested FlexUnit with. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Alex
Re: [VOTE] Accept Adobe Donation
+1 (Binding) Peter Ent Adobe Systems On 4/17/14 6:32 PM, Alex Harui aha...@adobe.com wrote: Please vote to accept the donation of the following Flex-related code and documentation from Adobe Systems, Inc. The vote will be open for at least 72 hours. Thanks, -Alex In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbui l der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex. h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklis t .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tri c ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html FlexPMD is currently on Open@Adobe here: http://sourceforge.net/adobe/flexpmd/home/Home/ The Mobile Trader demo application is described here: http://www.adobe.com/devnet/flex/samples/mobile-trader-application.html And here: http://coenraets.org/blog/2011/03/flex-on-the-ipad/ The XML merge utility is a small set of files that should have been in the BlazeDS donation Squiggly is described here: http://labs.adobe.com/technologies/squiggly/ Tour De Flex is described here: http://www.adobe.com/devnet/flex/tourdeflex.html
Re: Build Servers
Well, the sdk build mostly completes but is now stuck trying to launch flash player. I think I set the Jenkins service to have access to the display but that's not helping. Is there something else I need to do? -Alex On 4/20/14 11:22 PM, Alex Harui aha...@adobe.com wrote: Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: 4.12.1
Yes, I intend to take over Lee on this ticket, but not soon. If someone else would like to work on it before I do, no problem for me. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 avril 2014 14:46 À : dev@flex.apache.org Objet : Re: 4.12.1 https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
Re: 4.12.1
OK, I'll look into it. I just saw a commit from you. Is there anything else you want to get into 4.12.1? -Alex On 4/21/14 2:21 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Yes, I intend to take over Lee on this ticket, but not soon. If someone else would like to work on it before I do, no problem for me. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 avril 2014 14:46 À : dev@flex.apache.org Objet : Re: 4.12.1 https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
Re: Build Servers
On Apr 21, 2014 1:58 PM, Alex Harui aha...@adobe.com wrote: Well, the sdk build mostly completes but is now stuck trying to launch flash player. I think I set the Jenkins service to have access to the display but that's not helping. Is there something else I need to do? The job needs to run on a slave instance (same machine is fine) to have access to the windowing system. Thanks, Om -Alex On 4/20/14 11:22 PM, Alex Harui aha...@adobe.com wrote: Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: 4.12.1
Is there anything else you want to get into 4.12.1? I am working on the GC issue (FLEX-34230) Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 avril 2014 23:31 À : dev@flex.apache.org Objet : Re: 4.12.1 OK, I'll look into it. I just saw a commit from you. Is there anything else you want to get into 4.12.1? -Alex On 4/21/14 2:21 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Yes, I intend to take over Lee on this ticket, but not soon. If someone else would like to work on it before I do, no problem for me. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 avril 2014 14:46 À : dev@flex.apache.org Objet : Re: 4.12.1 https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
Re: Build Servers
On Apr 21, 2014 2:39 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Apr 21, 2014 1:58 PM, Alex Harui aha...@adobe.com wrote: Well, the sdk build mostly completes but is now stuck trying to launch flash player. I think I set the Jenkins service to have access to the display but that's not helping. Is there something else I need to do? The job needs to run on a slave instance (same machine is fine) to have access to the windowing system. More importantly, Jenkins running as a service will not be able access the display. The slave needs to be configured to start via JNLP. Thanks, Om Thanks, Om -Alex On 4/20/14 11:22 PM, Alex Harui aha...@adobe.com wrote: Hi Erik, Om, I actually spent my evenings this weekend trying to set it up. Figured I'd learn something about Jenkins and Azure in the process. I'll post the info on private@ and we should just send emails when/if you guys have time to spend on it. I'll be poking at it for another 40 minutes or so this evening. Feel free to change just about anything. Thanks, -Alex On 4/20/14 11:46 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Sun, Apr 20, 2014 at 11:35 AM, Erik de Bruin e...@ixsoftware.nl wrote: Just CI and nightlies, to replace 'builds@a.o'. Then if that is working reliably, we can start experimenting with your plan to add more Mustella nodes... Great. Can you make sure that the VMs are clone-able? You might have to create a fully working system, stop it, do a sysprep and create a clone before use that. It is a little bit of upfront work, but makes it so much easier to bring new systems online and get them working off the bat. Thanks, Om EdB On Sun, Apr 20, 2014 at 7:48 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Apr 20, 2014 10:24 AM, Erik de Bruin e...@ixsoftware.nl wrote: Alex, I may be able to free up some time this week to (help) create the CI VM. All I need are your Azure account credentials, so I can set up the VM, after which I can use RDP to set up the software for the builds. Free from 'builds@a.o', free at last! EdB What about Mustella? Our is this just for CI? On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui aha...@adobe.com wrote: After seeing this latest run of failures, does anybody still want to rely on build.a.o for anything? If anything, we should ask builds@ to email their list when they do critical security upgrades so we can try to keep up on our build machine. I think there's a chance that a multi-project server is likely to have a huge pile of jars from all over the place which is more exposed than the few jars for our flex-only server. We just have to learn how to harden it at least as well as builds.a.o. Shouldn't that be possible? And I have to admit that I'm tempted to point the next version of the installer out to our Flex CI server for its config or mirror the whole site. We can't even modify our site right now. -Alex On 4/17/14 3:58 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Do we want to at least use the ASF build server for providing official nightly dev builds? +1 We can resonably trust infra machines to be secure and that non one has fiddled with the nightly builds. Our own set up machines are likely to be less secure and there's a small risk that something bad could happen. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Build Servers
On 4/21/14 4:59 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: The job needs to run on a slave instance (same machine is fine) to have access to the windowing system. More importantly, Jenkins running as a service will not be able access the display. The slave needs to be configured to start via JNLP. OK, the player runs. Next problem is getting trace output. I think I've put mm.cfg in the right place. I'm off the VM for the next 2.5 hours. Time for dinner and stuff like that. Thanks, -Alex
Re: [VOTE] Apache Flex FalconJX 0.0.1 RC4
+1 (binding) Sigs ok Builds ok. Can be used in FlexJS builds Definitely agree this is the bare minimum to go public with. Still lots of work to get to 1.0. -Alex On 4/20/14 10:45 PM, Erik de Bruin e...@ixsoftware.nl wrote: +1 (binding) - sigs good - docs meager, but seem OK - 'ant all' target completes successfully (i.e. source builds and all tests pass) I'll go with Justin on this one and add that these aren't release quality bits, but I think it is a good move to release early and (hopefully) often, getting this new framework to where the wild things live ;-) EdB On Mon, Apr 21, 2014 at 2:09 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, +1 (binding) NOTICE, LICENCE, RELEASE_NOTE all OK (minor formatting/line length issues) checksum/sigs good rat report good can compile from source unit tests pass can use mxmlc and compc without error however can't use compiler.jx compc and mxmlc was (eventually) able to test compiler.jx with upstream FlexJS package Note if this wasn't an alpha I wouldn't vote +1 - documentation needs some work - compiler.jx compc and mxmlc don't work out of the box - relies on a upstream package to correctly test and not all tests/examples are working Tested on OSX. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [VOTE] Apache FlexJS 0.0.1 RC3
+1 (binding) Sigs ok Docs exist Source builds Examples build. Some actually run. -Alex On 4/20/14 11:01 PM, Erik de Bruin e...@ixsoftware.nl wrote: +1 (binding) - sigs OK - docs meagre but OK - source builds - DataBindingTest good for both SWF and JS Alpha, but already excellent! EdB On Mon, Apr 21, 2014 at 2:43 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, +1 (binding) NOTICE, LICENCE, RELEASE_NOTE all OK (very minor formatting/line length issues) checksum/sigs good rat report OK (frameworks/js/jshint.properties is missing header) no binaries in source (except images) can compile from source unit tests pass - although coverage is currently poor (eg one flex unit test testing setting a column label) Note if this wasn't an alpha I wouldn't vote +1 - documentation/setup instructions needs some work need eg list all dependancies and versions needed eg python, node etc etc - no list of known issues - poor test coverage - unclear which examples are working - ant in some examples directory fail Tested on OSX. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
