Re: AW: AW: AW: Will we have a new release out the door till 8th of September?
On 9/2/16, 12:12 AM, "Christofer Dutz" wrote: >Ok ... so what's the plan now? If we want to get a release out till next >Thursday, we should initiate the release process ... I guess you posted >the "Final Call" email again a few days ago so I think all should have >had time to put in what's needed now, everything else should go into the >next release. > > >I would really like to start this. Me too. Unfortunately, I've been unable to get PMC members to examine the CI build from the release branch and report their findings. People who plan to vote are supposed to examine the artifacts from the release branch and give a thumbs up before we make RCs to avoid the wasted time of creating and posting RCs and launching vote threads only to cancel them when folks actually start looking. Historically, that results in confusion about which RC someone examined and a lot of wasted energy. That said, I see from [1] that I was supposed to use [DISCUSS] instead of [LAST CALL] in my plea for examiners so I will try that now. -Alex [1] https://cwiki.apache.org/confluence/display/FLEX/A+guide+to+the+Apache+Flex +release+process
AW: AW: AW: Will we have a new release out the door till 8th of September?
Ok ... so what's the plan now? If we want to get a release out till next Thursday, we should initiate the release process ... I guess you posted the "Final Call" email again a few days ago so I think all should have had time to put in what's needed now, everything else should go into the next release. I would really like to start this. Chris Von: Alex Harui Gesendet: Freitag, 2. September 2016 02:35:27 An: dev@flex.apache.org Betreff: Re: AW: AW: Will we have a new release out the door till 8th of September? On 9/1/16, 2:12 PM, "Josh Tynjala" wrote: >Node has access to environment variables, so setting one could be a way to >switch between release and nightly builds. No need to comment code in and >out. It could work both when testing locally and when installing from NPM, >if implemented the right way. That sounds like a good solution to me. It doesn't have to be pretty, just possible. Thanks, -Alex
Re: AW: AW: Will we have a new release out the door till 8th of September?
On 9/1/16, 2:12 PM, "Josh Tynjala" wrote: >Node has access to environment variables, so setting one could be a way to >switch between release and nightly builds. No need to comment code in and >out. It could work both when testing locally and when installing from NPM, >if implemented the right way. That sounds like a good solution to me. It doesn't have to be pretty, just possible. Thanks, -Alex
Re: AW: AW: Will we have a new release out the door till 8th of September?
Node has access to environment variables, so setting one could be a way to switch between release and nightly builds. No need to comment code in and out. It could work both when testing locally and when installing from NPM, if implemented the right way. - Josh On Thu, Sep 1, 2016 at 1:44 PM, Alex Harui wrote: > IMO, the goal is to be able to test new packages on your local machine > without having to publish anything and without having to comment code in > and out. Some day we might change the package structure again, or even > change versions of dependencies. It might be nice to be able to offer npm > install of the nightly, but again, if the packaging of the nightly changes > and we need to tweak the scripts could we test those changes locally > without screwing up folks currently grabbing the nightly? > > My 2 cents, > -Alex > > On 9/1/16, 11:12 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > >On Thu, Sep 1, 2016 at 7:56 AM, Josh Tynjala > >wrote: > > > >> I don't think we can add extra options to the npm install command. I > >>just > >> did a quick test locally like this: > >> > >> npm install flexjs-0.7.0.tgz -g -extr > >> > >> In the download_dependencies.js script, I checked the value of > >> process.argv, and I could not see the "-extra" argument. > >> > >> However, NPM supports the concept of a "tag" for a release. Normally, > >>when > >> you publish to the registry, you publish to the "latest" tag. We could > >> publish a special version to a "nightly" tag that downloads nightly > >>builds > >> instead of release builds. > >> > >> Then, when you want a nightly build, you can do something like this: > >> > >> npm install flexjs@nightly -g > >> > >> A release version is still installed normally: > >> > >> npm install flexjs -g > >> > >> - Josh > >> > > > >We load all the urls, paths etc. from a special field in the package.json > >file. We should be able to set a flag here and handle it in code. This > >method could be used if we wanted more flexibility. > > > >Although, what Josh said should work fine as well. > > > >Thanks, > >Om > > > > > >> > >> On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui wrote: > >> > >> > Om, > >> > > >> > Is there a way to pick up command line parameters so we could use a > >> > –nightly flag to test against the nightly CI server instead of the > >> mirrors > >> > so we could have both code-paths in the repo and wouldn't have to > >> remember > >> > to revert some of this code? > >> > > >> > -Alex > >> > > >> > From: "omup...@gmail.com<mailto:omup...@gmail.com>" < > omup...@gmail.com > >> > <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < > >> > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> > >> > Date: Tuesday, August 30, 2016 at 12:53 PM > >> > To: Alex Harui mailto:aha...@adobe.com>> > >> > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < > >> dev@flex.apache.org > >> > <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com >> > harbs.li...@gmail.com>" >> > harbs.li...@gmail.com>> > >> > Subject: Re: AW: AW: Will we have a new release out the door till 8th > >>of > >> > September? > >> > > >> > I just looked over your changes. Looks fine to me. We should > >>remember > >> to > >> > revert the hardcoded paths of falcon/flexjs binaries to the mirror > >>urls > >> > once we push the release out. > >> > > >> > Then we can test the npm flexjs distribution one last time and push > >>the > >> > module out to npmjs.org<http://npmjs.org> > >> > > >> > Thanks for pushing this out. It would have taken quite a long time > >>for > >> me > >> > to figure out all the changes. > >> > > >> > Regards, > >> > Om > >> > > >> > On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui >> > aha...@adobe.com>> wrote: > >> > OK, I just pushed changes that seem to work with the nightly build. I > >> > think we have to update the scripts once more once the final release >
Re: AW: AW: Will we have a new release out the door till 8th of September?
IMO, the goal is to be able to test new packages on your local machine without having to publish anything and without having to comment code in and out. Some day we might change the package structure again, or even change versions of dependencies. It might be nice to be able to offer npm install of the nightly, but again, if the packaging of the nightly changes and we need to tweak the scripts could we test those changes locally without screwing up folks currently grabbing the nightly? My 2 cents, -Alex On 9/1/16, 11:12 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Thu, Sep 1, 2016 at 7:56 AM, Josh Tynjala >wrote: > >> I don't think we can add extra options to the npm install command. I >>just >> did a quick test locally like this: >> >> npm install flexjs-0.7.0.tgz -g -extr >> >> In the download_dependencies.js script, I checked the value of >> process.argv, and I could not see the "-extra" argument. >> >> However, NPM supports the concept of a "tag" for a release. Normally, >>when >> you publish to the registry, you publish to the "latest" tag. We could >> publish a special version to a "nightly" tag that downloads nightly >>builds >> instead of release builds. >> >> Then, when you want a nightly build, you can do something like this: >> >> npm install flexjs@nightly -g >> >> A release version is still installed normally: >> >> npm install flexjs -g >> >> - Josh >> > >We load all the urls, paths etc. from a special field in the package.json >file. We should be able to set a flag here and handle it in code. This >method could be used if we wanted more flexibility. > >Although, what Josh said should work fine as well. > >Thanks, >Om > > >> >> On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui wrote: >> >> > Om, >> > >> > Is there a way to pick up command line parameters so we could use a >> > –nightly flag to test against the nightly CI server instead of the >> mirrors >> > so we could have both code-paths in the repo and wouldn't have to >> remember >> > to revert some of this code? >> > >> > -Alex >> > >> > From: "omup...@gmail.com<mailto:omup...@gmail.com>" > > <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < >> > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> >> > Date: Tuesday, August 30, 2016 at 12:53 PM >> > To: Alex Harui mailto:aha...@adobe.com>> >> > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < >> dev@flex.apache.org >> > <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com> > harbs.li...@gmail.com>" > > harbs.li...@gmail.com>> >> > Subject: Re: AW: AW: Will we have a new release out the door till 8th >>of >> > September? >> > >> > I just looked over your changes. Looks fine to me. We should >>remember >> to >> > revert the hardcoded paths of falcon/flexjs binaries to the mirror >>urls >> > once we push the release out. >> > >> > Then we can test the npm flexjs distribution one last time and push >>the >> > module out to npmjs.org<http://npmjs.org> >> > >> > Thanks for pushing this out. It would have taken quite a long time >>for >> me >> > to figure out all the changes. >> > >> > Regards, >> > Om >> > >> > On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui > > aha...@adobe.com>> wrote: >> > OK, I just pushed changes that seem to work with the nightly build. I >> > think we have to update the scripts once more once the final release >>is >> out >> > on the mirrors. Then is there a final step where we publish this >>module >> to >> > the uber Node registry? >> > >> > I would like to have at least one more PMC member review the release >> > before we cut RCs. I will post more information in the Last Call >>thread >> in >> > case folks are filtering for that. >> > >> > -Alex >> > >> > From: "omup...@gmail.com<mailto:omup...@gmail.com>" > > <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < >> > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> >> > Date: Monday, August 29, 2016 at 12:37 PM >> > To: Alex Harui mailto:aha...@adobe.com>> >> > Cc: "dev@flex.apache.or
Re: AW: AW: Will we have a new release out the door till 8th of September?
On Thu, Sep 1, 2016 at 7:56 AM, Josh Tynjala wrote: > I don't think we can add extra options to the npm install command. I just > did a quick test locally like this: > > npm install flexjs-0.7.0.tgz -g -extr > > In the download_dependencies.js script, I checked the value of > process.argv, and I could not see the "-extra" argument. > > However, NPM supports the concept of a "tag" for a release. Normally, when > you publish to the registry, you publish to the "latest" tag. We could > publish a special version to a "nightly" tag that downloads nightly builds > instead of release builds. > > Then, when you want a nightly build, you can do something like this: > > npm install flexjs@nightly -g > > A release version is still installed normally: > > npm install flexjs -g > > - Josh > We load all the urls, paths etc. from a special field in the package.json file. We should be able to set a flag here and handle it in code. This method could be used if we wanted more flexibility. Although, what Josh said should work fine as well. Thanks, Om > > On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui wrote: > > > Om, > > > > Is there a way to pick up command line parameters so we could use a > > –nightly flag to test against the nightly CI server instead of the > mirrors > > so we could have both code-paths in the repo and wouldn't have to > remember > > to revert some of this code? > > > > -Alex > > > > From: "omup...@gmail.com<mailto:omup...@gmail.com>" > <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < > > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> > > Date: Tuesday, August 30, 2016 at 12:53 PM > > To: Alex Harui mailto:aha...@adobe.com>> > > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < > dev@flex.apache.org > > <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com > harbs.li...@gmail.com>" > harbs.li...@gmail.com>> > > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > > September? > > > > I just looked over your changes. Looks fine to me. We should remember > to > > revert the hardcoded paths of falcon/flexjs binaries to the mirror urls > > once we push the release out. > > > > Then we can test the npm flexjs distribution one last time and push the > > module out to npmjs.org<http://npmjs.org> > > > > Thanks for pushing this out. It would have taken quite a long time for > me > > to figure out all the changes. > > > > Regards, > > Om > > > > On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui > aha...@adobe.com>> wrote: > > OK, I just pushed changes that seem to work with the nightly build. I > > think we have to update the scripts once more once the final release is > out > > on the mirrors. Then is there a final step where we publish this module > to > > the uber Node registry? > > > > I would like to have at least one more PMC member review the release > > before we cut RCs. I will post more information in the Last Call thread > in > > case folks are filtering for that. > > > > -Alex > > > > From: "omup...@gmail.com<mailto:omup...@gmail.com>" > <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < > > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> > > Date: Monday, August 29, 2016 at 12:37 PM > > To: Alex Harui mailto:aha...@adobe.com>> > > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < > dev@flex.apache.org > > <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com > harbs.li...@gmail.com>" > harbs.li...@gmail.com>> > > > > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > > September? > > > > Locally, you can test by simply running: > > > > Install: npm install -g > > Uninstall: npm uninstall flexjs -g > > > > If you want to test the one deployed on npm, you need to run: > > Install: npm install flexjs -g > > Uninstall: npm uninstall flexjs -g > > > > Installing will add the flexjs module to: > > > > Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ > > Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ > > > > On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui > aha...@adobe.com>> wrote: > > How do you test changes? > > > > Sent from my LG G3, an AT&T 4G LTE smartphone > > > > --
Re: AW: AW: Will we have a new release out the door till 8th of September?
I don't think we can add extra options to the npm install command. I just did a quick test locally like this: npm install flexjs-0.7.0.tgz -g -extr In the download_dependencies.js script, I checked the value of process.argv, and I could not see the "-extra" argument. However, NPM supports the concept of a "tag" for a release. Normally, when you publish to the registry, you publish to the "latest" tag. We could publish a special version to a "nightly" tag that downloads nightly builds instead of release builds. Then, when you want a nightly build, you can do something like this: npm install flexjs@nightly -g A release version is still installed normally: npm install flexjs -g - Josh On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui wrote: > Om, > > Is there a way to pick up command line parameters so we could use a > –nightly flag to test against the nightly CI server instead of the mirrors > so we could have both code-paths in the repo and wouldn't have to remember > to revert some of this code? > > -Alex > > From: "omup...@gmail.com<mailto:omup...@gmail.com>" <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> > Date: Tuesday, August 30, 2016 at 12:53 PM > To: Alex Harui mailto:aha...@adobe.com>> > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com harbs.li...@gmail.com>" harbs.li...@gmail.com>> > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > September? > > I just looked over your changes. Looks fine to me. We should remember to > revert the hardcoded paths of falcon/flexjs binaries to the mirror urls > once we push the release out. > > Then we can test the npm flexjs distribution one last time and push the > module out to npmjs.org<http://npmjs.org> > > Thanks for pushing this out. It would have taken quite a long time for me > to figure out all the changes. > > Regards, > Om > > On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui aha...@adobe.com>> wrote: > OK, I just pushed changes that seem to work with the nightly build. I > think we have to update the scripts once more once the final release is out > on the mirrors. Then is there a final step where we publish this module to > the uber Node registry? > > I would like to have at least one more PMC member review the release > before we cut RCs. I will post more information in the Last Call thread in > case folks are filtering for that. > > -Alex > > From: "omup...@gmail.com<mailto:omup...@gmail.com>" <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala < > bigosma...@gmail.com<mailto:bigosma...@gmail.com>> > Date: Monday, August 29, 2016 at 12:37 PM > To: Alex Harui mailto:aha...@adobe.com>> > Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com harbs.li...@gmail.com>" harbs.li...@gmail.com>> > > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > September? > > Locally, you can test by simply running: > > Install: npm install -g > Uninstall: npm uninstall flexjs -g > > If you want to test the one deployed on npm, you need to run: > Install: npm install flexjs -g > Uninstall: npm uninstall flexjs -g > > Installing will add the flexjs module to: > > Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ > Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ > > On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui aha...@adobe.com>> wrote: > How do you test changes? > > Sent from my LG G3, an AT&T 4G LTE smartphone > > -- Original message-- > From: OmPrakash Muppirala > Date: Mon, Aug 29, 2016 11:30 AM > To: dev@flex.apache.org<mailto:dev@flex.apache.org>; > Cc: Harbs; > Subject:Re: AW: AW: Will we have a new release out the door till 8th of > September? > > Still on it. Sorry it turned out to be more work than I thought. Hope to > get it done soon. > > Unless someone wants to jump in and help out. Looks like most of the > changes are in this file: > > https://github.com/apache/flex-utilities/blob/develop/ > npm-flexjs/dependencies/ApacheFalcon.js > > Thanks, > Om > > On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui mailto:aharu > i...@adobe.com>> wrote: > > > > > > > On 8/29/16, 12:31 AM, "Christofer Dutz" mailto:christofer.d...@c-ware.de>> wrote: > > > > >So what's the state on this? > > > > I was hoping to hear from Om that the npm was working again. And I was > > hoping to hear from at least one more PMC member that they checked the > > release packages and they looked ok. Have you done that? Plus, at least > > 3 PMC members were on the road last week. I'd like to get a vote going > by > > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > > never done it before. > > > > -Alex > > > > > > >
Re: AW: AW: AW: AW: Will we have a new release out the door till 8th of September?
On 8/31/16, 12:30 AM, "Christofer Dutz" wrote: >No not talking about NPM ... we were talking about adding things to the >Xml file where all the URLs are pulled from. And in that context I was >asking to add the Flash Player Content Debugger. I am planning on >automating even the last part of the Maven build, The setting of the >FLASHPLAYER_DEBUGGER environment variable. As I wrote, I currently >calculate the URL in the code, but would really like to have it in the >xml as we could change that without re-releasing the mavenizer, in case >Adobe reorganized their URLs. You are welcome to add another section to sdk-installer-config-4.0.xml. -Alex
AW: AW: AW: AW: Will we have a new release out the door till 8th of September?
No not talking about NPM ... we were talking about adding things to the Xml file where all the URLs are pulled from. And in that context I was asking to add the Flash Player Content Debugger. I am planning on automating even the last part of the Maven build, The setting of the FLASHPLAYER_DEBUGGER environment variable. As I wrote, I currently calculate the URL in the code, but would really like to have it in the xml as we could change that without re-releasing the mavenizer, in case Adobe reorganized their URLs. Chris Von: Alex Harui Gesendet: Mittwoch, 31. August 2016 08:43:32 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: Will we have a new release out the door till 8th of September? On 8/30/16, 11:27 PM, "Christofer Dutz" wrote: >Would be cool if we could add the urls to the flash placer content >debuggers as currently I'm hard coding the url-scheme in the mavenizer >code. Do you mean have NPM bring down the projector debugger? It is only needed for running tests, most folks building apps shouldn't needed it. I've thought about Ant/NPM scripts that bring down the prerequisites but have been concerned about making appear like dependencies and causing confusion. -Alex
Re: AW: AW: AW: Will we have a new release out the door till 8th of September?
On 8/30/16, 11:27 PM, "Christofer Dutz" wrote: >Would be cool if we could add the urls to the flash placer content >debuggers as currently I'm hard coding the url-scheme in the mavenizer >code. Do you mean have NPM bring down the projector debugger? It is only needed for running tests, most folks building apps shouldn't needed it. I've thought about Ant/NPM scripts that bring down the prerequisites but have been concerned about making appear like dependencies and causing confusion. -Alex
AW: AW: AW: Will we have a new release out the door till 8th of September?
Would be cool if we could add the urls to the flash placer content debuggers as currently I'm hard coding the url-scheme in the mavenizer code. Chris Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Alex Harui Datum: 30.08.16 22:33 (GMT+01:00) An: OmPrakash Muppirala Cc: dev@flex.apache.org, harbs.li...@gmail.com Betreff: Re: AW: AW: Will we have a new release out the door till 8th of September? Well, right now, the install() methods have a request() call that is commented out in favor of a get() call. The request call is set up to call the mirrors.cgi, the get() call is set up to grab the nightly. If the install() method could have a parameter passed to it, then we wouldn't have to comment out one path or the other and could just run with an additional parameter to get the nightly, and no parameter hits the mirror.cgi. I could imagine even more sophisticated code that grabs the latest release URLs from the same place as the installer so we don't have to update the npm scripts as often and maybe lets you choose a version, but that doesn't seem that important to me. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Tuesday, August 30, 2016 at 1:00 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Sure we could do that. Can you give more requirements on how the command line switch would need to work? I can try to add this as soon as possible. Thanks, Om On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui mailto:aha...@adobe.com>> wrote: Om, Is there a way to pick up command line parameters so we could use a –nightly flag to test against the nightly CI server instead of the mirrors so we could have both code-paths in the repo and wouldn't have to remember to revert some of this code? -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Tuesday, August 30, 2016 at 12:53 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? I just looked over your changes. Looks fine to me. We should remember to revert the hardcoded paths of falcon/flexjs binaries to the mirror urls once we push the release out. Then we can test the npm flexjs distribution one last time and push the module out to npmjs.org<http://npmjs.org> Thanks for pushing this out. It would have taken quite a long time for me to figure out all the changes. Regards, Om On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui mailto:aha...@adobe.com>> wrote: OK, I just pushed changes that seem to work with the nightly build. I think we have to update the scripts once more once the final release is out on the mirrors. Then is there a final step where we publish this module to the uber Node registry? I would like to have at least one more PMC member review the release before we cut RCs. I will post more information in the Last Call thread in case folks are filtering for that. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Monday, August 29, 2016 at 12:37 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Locally, you can test by simply running: Install: npm install -g Uninstall: npm uninstall flexjs -g If you want to test the one deployed on npm, you need to run: Install: npm install flexjs -g Uninstall: npm uninstall flexjs -g Installing will add the flexjs module to: Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui mailto:aha...@adobe.com>> wrote: How do you test changes? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Mon, Aug 29, 2016 11:30 AM To: dev@flex.apach
Re: AW: AW: Will we have a new release out the door till 8th of September?
Well, right now, the install() methods have a request() call that is commented out in favor of a get() call. The request call is set up to call the mirrors.cgi, the get() call is set up to grab the nightly. If the install() method could have a parameter passed to it, then we wouldn't have to comment out one path or the other and could just run with an additional parameter to get the nightly, and no parameter hits the mirror.cgi. I could imagine even more sophisticated code that grabs the latest release URLs from the same place as the installer so we don't have to update the npm scripts as often and maybe lets you choose a version, but that doesn't seem that important to me. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Tuesday, August 30, 2016 at 1:00 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Sure we could do that. Can you give more requirements on how the command line switch would need to work? I can try to add this as soon as possible. Thanks, Om On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui mailto:aha...@adobe.com>> wrote: Om, Is there a way to pick up command line parameters so we could use a –nightly flag to test against the nightly CI server instead of the mirrors so we could have both code-paths in the repo and wouldn't have to remember to revert some of this code? -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Tuesday, August 30, 2016 at 12:53 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? I just looked over your changes. Looks fine to me. We should remember to revert the hardcoded paths of falcon/flexjs binaries to the mirror urls once we push the release out. Then we can test the npm flexjs distribution one last time and push the module out to npmjs.org<http://npmjs.org> Thanks for pushing this out. It would have taken quite a long time for me to figure out all the changes. Regards, Om On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui mailto:aha...@adobe.com>> wrote: OK, I just pushed changes that seem to work with the nightly build. I think we have to update the scripts once more once the final release is out on the mirrors. Then is there a final step where we publish this module to the uber Node registry? I would like to have at least one more PMC member review the release before we cut RCs. I will post more information in the Last Call thread in case folks are filtering for that. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Monday, August 29, 2016 at 12:37 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Locally, you can test by simply running: Install: npm install -g Uninstall: npm uninstall flexjs -g If you want to test the one deployed on npm, you need to run: Install: npm install flexjs -g Uninstall: npm uninstall flexjs -g Installing will add the flexjs module to: Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui mailto:aha...@adobe.com>> wrote: How do you test changes? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Mon, Aug 29, 2016 11:30 AM To: dev@flex.apache.org<mailto:dev@flex.apache.org>; Cc: Harbs; Subject:Re: AW: AW: Will we have a new release out the door till 8th of September? Still on it. Sorry it turned out to be more work than I thought. Hope to get it done soon. Unless someone wants to jump in and help out. Looks like most of the changes are in this file: https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependencies/ApacheFalcon.js Thanks, Om On Mon, Aug 29, 2016 at 7:
Re: AW: AW: Will we have a new release out the door till 8th of September?
Sure we could do that. Can you give more requirements on how the command line switch would need to work? I can try to add this as soon as possible. Thanks, Om On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui wrote: > Om, > > Is there a way to pick up command line parameters so we could use a > –nightly flag to test against the nightly CI server instead of the mirrors > so we could have both code-paths in the repo and wouldn't have to remember > to revert some of this code? > > -Alex > > From: "omup...@gmail.com" on behalf of OmPrakash > Muppirala > Date: Tuesday, August 30, 2016 at 12:53 PM > > To: Alex Harui > Cc: "dev@flex.apache.org" , "harbs.li...@gmail.com" < > harbs.li...@gmail.com> > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > September? > > I just looked over your changes. Looks fine to me. We should remember to > revert the hardcoded paths of falcon/flexjs binaries to the mirror urls > once we push the release out. > > Then we can test the npm flexjs distribution one last time and push the > module out to npmjs.org > > Thanks for pushing this out. It would have taken quite a long time for me > to figure out all the changes. > > Regards, > Om > > On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui wrote: > >> OK, I just pushed changes that seem to work with the nightly build. I >> think we have to update the scripts once more once the final release is out >> on the mirrors. Then is there a final step where we publish this module to >> the uber Node registry? >> >> I would like to have at least one more PMC member review the release >> before we cut RCs. I will post more information in the Last Call thread in >> case folks are filtering for that. >> >> -Alex >> >> From: "omup...@gmail.com" on behalf of OmPrakash >> Muppirala >> Date: Monday, August 29, 2016 at 12:37 PM >> To: Alex Harui >> Cc: "dev@flex.apache.org" , "harbs.li...@gmail.com" >> >> >> Subject: Re: AW: AW: Will we have a new release out the door till 8th of >> September? >> >> Locally, you can test by simply running: >> >> Install: npm install -g >> Uninstall: npm uninstall flexjs -g >> >> If you want to test the one deployed on npm, you need to run: >> Install: npm install flexjs -g >> Uninstall: npm uninstall flexjs -g >> >> Installing will add the flexjs module to: >> >> Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ >> Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ >> >> On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui wrote: >> >>> How do you test changes? >>> >>> Sent from my LG G3, an AT&T 4G LTE smartphone >>> >>> -- Original message-- >>> *From: *OmPrakash Muppirala >>> *Date: *Mon, Aug 29, 2016 11:30 AM >>> *To: *dev@flex.apache.org; >>> *Cc: *Harbs; >>> *Subject:*Re: AW: AW: Will we have a new release out the door till 8th >>> of September? >>> >>> Still on it. Sorry it turned out to be more work than I thought. Hope >>> to >>> get it done soon. >>> >>> Unless someone wants to jump in and help out. Looks like most of the >>> changes are in this file: >>> >>> https://github.com/apache/flex-utilities/blob/develop/npm-fl >>> exjs/dependencies/ApacheFalcon.js >>> >>> Thanks, >>> Om >>> >>> On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui wrote: >>> >>> > >>> > >>> > On 8/29/16, 12:31 AM, "Christofer Dutz" >>> wrote: >>> > >>> > >So what's the state on this? >>> > >>> > I was hoping to hear from Om that the npm was working again. And I was >>> > hoping to hear from at least one more PMC member that they checked the >>> > release packages and they looked ok. Have you done that? Plus, at >>> least >>> > 3 PMC members were on the road last week. I'd like to get a vote >>> going by >>> > Tuesday or Wednesday. I might be able to work on the npm stuff, but >>> I've >>> > never done it before. >>> > >>> > -Alex >>> > >>> > >>> >> >> >
Re: AW: AW: Will we have a new release out the door till 8th of September?
Om, Is there a way to pick up command line parameters so we could use a –nightly flag to test against the nightly CI server instead of the mirrors so we could have both code-paths in the repo and wouldn't have to remember to revert some of this code? -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Tuesday, August 30, 2016 at 12:53 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? I just looked over your changes. Looks fine to me. We should remember to revert the hardcoded paths of falcon/flexjs binaries to the mirror urls once we push the release out. Then we can test the npm flexjs distribution one last time and push the module out to npmjs.org<http://npmjs.org> Thanks for pushing this out. It would have taken quite a long time for me to figure out all the changes. Regards, Om On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui mailto:aha...@adobe.com>> wrote: OK, I just pushed changes that seem to work with the nightly build. I think we have to update the scripts once more once the final release is out on the mirrors. Then is there a final step where we publish this module to the uber Node registry? I would like to have at least one more PMC member review the release before we cut RCs. I will post more information in the Last Call thread in case folks are filtering for that. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Monday, August 29, 2016 at 12:37 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Locally, you can test by simply running: Install: npm install -g Uninstall: npm uninstall flexjs -g If you want to test the one deployed on npm, you need to run: Install: npm install flexjs -g Uninstall: npm uninstall flexjs -g Installing will add the flexjs module to: Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui mailto:aha...@adobe.com>> wrote: How do you test changes? Sent from my LG G3, an AT&T 4G LTE smartphone ------ Original message-- From: OmPrakash Muppirala Date: Mon, Aug 29, 2016 11:30 AM To: dev@flex.apache.org<mailto:dev@flex.apache.org>; Cc: Harbs; Subject:Re: AW: AW: Will we have a new release out the door till 8th of September? Still on it. Sorry it turned out to be more work than I thought. Hope to get it done soon. Unless someone wants to jump in and help out. Looks like most of the changes are in this file: https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependencies/ApacheFalcon.js Thanks, Om On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui mailto:aha...@adobe.com>> wrote: > > > On 8/29/16, 12:31 AM, "Christofer Dutz" > mailto:christofer.d...@c-ware.de>> wrote: > > >So what's the state on this? > > I was hoping to hear from Om that the npm was working again. And I was > hoping to hear from at least one more PMC member that they checked the > release packages and they looked ok. Have you done that? Plus, at least > 3 PMC members were on the road last week. I'd like to get a vote going by > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > never done it before. > > -Alex > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
I just looked over your changes. Looks fine to me. We should remember to revert the hardcoded paths of falcon/flexjs binaries to the mirror urls once we push the release out. Then we can test the npm flexjs distribution one last time and push the module out to npmjs.org Thanks for pushing this out. It would have taken quite a long time for me to figure out all the changes. Regards, Om On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui wrote: > OK, I just pushed changes that seem to work with the nightly build. I > think we have to update the scripts once more once the final release is out > on the mirrors. Then is there a final step where we publish this module to > the uber Node registry? > > I would like to have at least one more PMC member review the release > before we cut RCs. I will post more information in the Last Call thread in > case folks are filtering for that. > > -Alex > > From: "omup...@gmail.com" on behalf of OmPrakash > Muppirala > Date: Monday, August 29, 2016 at 12:37 PM > To: Alex Harui > Cc: "dev@flex.apache.org" , "harbs.li...@gmail.com" < > harbs.li...@gmail.com> > > Subject: Re: AW: AW: Will we have a new release out the door till 8th of > September? > > Locally, you can test by simply running: > > Install: npm install -g > Uninstall: npm uninstall flexjs -g > > If you want to test the one deployed on npm, you need to run: > Install: npm install flexjs -g > Uninstall: npm uninstall flexjs -g > > Installing will add the flexjs module to: > > Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ > Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ > > On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui wrote: > >> How do you test changes? >> >> Sent from my LG G3, an AT&T 4G LTE smartphone >> >> ------ Original message-- >> *From: *OmPrakash Muppirala >> *Date: *Mon, Aug 29, 2016 11:30 AM >> *To: *dev@flex.apache.org; >> *Cc: *Harbs; >> *Subject:*Re: AW: AW: Will we have a new release out the door till 8th >> of September? >> >> Still on it. Sorry it turned out to be more work than I thought. Hope to >> get it done soon. >> >> Unless someone wants to jump in and help out. Looks like most of the >> changes are in this file: >> >> https://github.com/apache/flex-utilities/blob/develop/npm- >> flexjs/dependencies/ApacheFalcon.js >> >> Thanks, >> Om >> >> On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui wrote: >> >> > >> > >> > On 8/29/16, 12:31 AM, "Christofer Dutz" >> wrote: >> > >> > >So what's the state on this? >> > >> > I was hoping to hear from Om that the npm was working again. And I was >> > hoping to hear from at least one more PMC member that they checked the >> > release packages and they looked ok. Have you done that? Plus, at >> least >> > 3 PMC members were on the road last week. I'd like to get a vote going >> by >> > Tuesday or Wednesday. I might be able to work on the npm stuff, but >> I've >> > never done it before. >> > >> > -Alex >> > >> > >> > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
OK, I just pushed changes that seem to work with the nightly build. I think we have to update the scripts once more once the final release is out on the mirrors. Then is there a final step where we publish this module to the uber Node registry? I would like to have at least one more PMC member review the release before we cut RCs. I will post more information in the Last Call thread in case folks are filtering for that. -Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Monday, August 29, 2016 at 12:37 PM To: Alex Harui mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>>, "harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>" mailto:harbs.li...@gmail.com>> Subject: Re: AW: AW: Will we have a new release out the door till 8th of September? Locally, you can test by simply running: Install: npm install -g Uninstall: npm uninstall flexjs -g If you want to test the one deployed on npm, you need to run: Install: npm install flexjs -g Uninstall: npm uninstall flexjs -g Installing will add the flexjs module to: Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui mailto:aha...@adobe.com>> wrote: How do you test changes? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Mon, Aug 29, 2016 11:30 AM To: dev@flex.apache.org<mailto:dev@flex.apache.org>; Cc: Harbs; Subject:Re: AW: AW: Will we have a new release out the door till 8th of September? Still on it. Sorry it turned out to be more work than I thought. Hope to get it done soon. Unless someone wants to jump in and help out. Looks like most of the changes are in this file: https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependencies/ApacheFalcon.js Thanks, Om On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui mailto:aha...@adobe.com>> wrote: > > > On 8/29/16, 12:31 AM, "Christofer Dutz" > mailto:christofer.d...@c-ware.de>> wrote: > > >So what's the state on this? > > I was hoping to hear from Om that the npm was working again. And I was > hoping to hear from at least one more PMC member that they checked the > release packages and they looked ok. Have you done that? Plus, at least > 3 PMC members were on the road last week. I'd like to get a vote going by > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > never done it before. > > -Alex > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
Locally, you can test by simply running: Install: npm install -g Uninstall: npm uninstall flexjs -g If you want to test the one deployed on npm, you need to run: Install: npm install flexjs -g Uninstall: npm uninstall flexjs -g Installing will add the flexjs module to: Windows: C:\Users\\AppData\Roaming\npm\node_modules\flexjs\ Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/ On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui wrote: > How do you test changes? > > Sent from my LG G3, an AT&T 4G LTE smartphone > > -- Original message-- > *From: *OmPrakash Muppirala > *Date: *Mon, Aug 29, 2016 11:30 AM > *To: *dev@flex.apache.org; > *Cc: *Harbs; > *Subject:*Re: AW: AW: Will we have a new release out the door till 8th of > September? > > Still on it. Sorry it turned out to be more work than I thought. Hope to > get it done soon. > > Unless someone wants to jump in and help out. Looks like most of the > changes are in this file: > > https://github.com/apache/flex-utilities/blob/develop/ > npm-flexjs/dependencies/ApacheFalcon.js > > Thanks, > Om > > On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui wrote: > > > > > > > On 8/29/16, 12:31 AM, "Christofer Dutz" > wrote: > > > > >So what's the state on this? > > > > I was hoping to hear from Om that the npm was working again. And I was > > hoping to hear from at least one more PMC member that they checked the > > release packages and they looked ok. Have you done that? Plus, at least > > 3 PMC members were on the road last week. I'd like to get a vote going > by > > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > > never done it before. > > > > -Alex > > > > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
How do you test changes? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Mon, Aug 29, 2016 11:30 AM To: dev@flex.apache.org; Cc: Harbs; Subject:Re: AW: AW: Will we have a new release out the door till 8th of September? Still on it. Sorry it turned out to be more work than I thought. Hope to get it done soon. Unless someone wants to jump in and help out. Looks like most of the changes are in this file: https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependencies/ApacheFalcon.js Thanks, Om On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui wrote: > > > On 8/29/16, 12:31 AM, "Christofer Dutz" wrote: > > >So what's the state on this? > > I was hoping to hear from Om that the npm was working again. And I was > hoping to hear from at least one more PMC member that they checked the > release packages and they looked ok. Have you done that? Plus, at least > 3 PMC members were on the road last week. I'd like to get a vote going by > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > never done it before. > > -Alex > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
Still on it. Sorry it turned out to be more work than I thought. Hope to get it done soon. Unless someone wants to jump in and help out. Looks like most of the changes are in this file: https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependencies/ApacheFalcon.js Thanks, Om On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui wrote: > > > On 8/29/16, 12:31 AM, "Christofer Dutz" wrote: > > >So what's the state on this? > > I was hoping to hear from Om that the npm was working again. And I was > hoping to hear from at least one more PMC member that they checked the > release packages and they looked ok. Have you done that? Plus, at least > 3 PMC members were on the road last week. I'd like to get a vote going by > Tuesday or Wednesday. I might be able to work on the npm stuff, but I've > never done it before. > > -Alex > >
Re: AW: AW: Will we have a new release out the door till 8th of September?
On 8/29/16, 12:31 AM, "Christofer Dutz" wrote: >So what's the state on this? I was hoping to hear from Om that the npm was working again. And I was hoping to hear from at least one more PMC member that they checked the release packages and they looked ok. Have you done that? Plus, at least 3 PMC members were on the road last week. I'd like to get a vote going by Tuesday or Wednesday. I might be able to work on the npm stuff, but I've never done it before. -Alex
AW: AW: Will we have a new release out the door till 8th of September?
So what's the state on this? Chris Von: omup...@gmail.com im Auftrag von OmPrakash Muppirala Gesendet: Montag, 22. August 2016 10:34:15 An: dev@flex.apache.org Cc: Harbs Betreff: Re: AW: Will we have a new release out the door till 8th of September? On Aug 22, 2016 1:05 AM, "Christofer Dutz" wrote: > > Ok ... so what's the current status on this? I was a little consumed during the weekend, but I noticed some NPM related problems. Are they resolved yet? > Not yet. Worked on it a little bit over the weekend. Still need to fix the falcon bits. Hopefully in the next couple of days... Thanks, Om > > Chris > > > Von: Alex Harui > Gesendet: Samstag, 20. August 2016 20:41:16 > An: harbs.li...@gmail.com; dev@flex.apache.org > Betreff: Re: Will we have a new release out the door till 8th of September? > > Aiui the method bodies are derived from openfl and look similar enough that we should at least give credit in license. It is easy enough to add a header too. > > Sent from my LG G3, an AT&T 4G LTE smartphone > > -- Original message-- > From: Harbs > Date: Sat, Aug 20, 2016 11:19 AM > To: dev@flex.apache.org; > Subject:Re: Will we have a new release out the door till 8th of September? > > It’s also not an exact copy of anything. I’d say it’s owned by Apache and no need for anything else. > > FYI, I’m going to be off the grid for most of the week. > > On Aug 20, 2016, at 5:36 PM, Alex Harui wrote: > > > When I look at Matrix.as it appears that Harbs added ASDoc. >
Re: AW: Will we have a new release out the door till 8th of September?
On Aug 22, 2016 1:05 AM, "Christofer Dutz" wrote: > > Ok ... so what's the current status on this? I was a little consumed during the weekend, but I noticed some NPM related problems. Are they resolved yet? > Not yet. Worked on it a little bit over the weekend. Still need to fix the falcon bits. Hopefully in the next couple of days... Thanks, Om > > Chris > > > Von: Alex Harui > Gesendet: Samstag, 20. August 2016 20:41:16 > An: harbs.li...@gmail.com; dev@flex.apache.org > Betreff: Re: Will we have a new release out the door till 8th of September? > > Aiui the method bodies are derived from openfl and look similar enough that we should at least give credit in license. It is easy enough to add a header too. > > Sent from my LG G3, an AT&T 4G LTE smartphone > > -- Original message-- > From: Harbs > Date: Sat, Aug 20, 2016 11:19 AM > To: dev@flex.apache.org; > Subject:Re: Will we have a new release out the door till 8th of September? > > It’s also not an exact copy of anything. I’d say it’s owned by Apache and no need for anything else. > > FYI, I’m going to be off the grid for most of the week. > > On Aug 20, 2016, at 5:36 PM, Alex Harui wrote: > > > When I look at Matrix.as it appears that Harbs added ASDoc. >
AW: Will we have a new release out the door till 8th of September?
Ok ... so what's the current status on this? I was a little consumed during the weekend, but I noticed some NPM related problems. Are they resolved yet? Chris Von: Alex Harui Gesendet: Samstag, 20. August 2016 20:41:16 An: harbs.li...@gmail.com; dev@flex.apache.org Betreff: Re: Will we have a new release out the door till 8th of September? Aiui the method bodies are derived from openfl and look similar enough that we should at least give credit in license. It is easy enough to add a header too. Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Harbs Date: Sat, Aug 20, 2016 11:19 AM To: dev@flex.apache.org; Subject:Re: Will we have a new release out the door till 8th of September? It’s also not an exact copy of anything. I’d say it’s owned by Apache and no need for anything else. FYI, I’m going to be off the grid for most of the week. On Aug 20, 2016, at 5:36 PM, Alex Harui wrote: > When I look at Matrix.as it appears that Harbs added ASDoc.
Re: AW: Will we have a new release out the door till 8th of September?
We are releasing everything. I believe Justin and I are agreeing that the falcon-only packages don't need review The falconjx packages contain falcon. Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Christofer Dutz Date: Sat, Aug 20, 2016 1:19 AM To: dev@flex.apache.org; Subject:AW: Will we have a new release out the door till 8th of September? But in jest to release Maven stuff we need a release of falcon to. I dud two-factor quit a lot of the structure there and falcon an falconjx are both part of the same Maven build. Is there a reason for not releasing everything? Chris Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Alex Harui Datum: 20.08.16 08:59 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: Will we have a new release out the door till 8th of September? Thanks for the timely review. On 8/19/16, 4:58 PM, "Justin Mclean" wrote: >Hi, > >For FlexJS: > >I can see that mention of OpenFL has been added to LICENSE, however the >file in question [1] has an Apache license header (not MIT as I think it >should be). We’re also not following the terms of it's MIT license [2] to >include the copyright and full text of the license. Usually you add that >as a pointer to the license file in the LICENSE [3] and / or leave the >full text in the header. > >We also have the same issue with Flat UI i.e. missing the copyright and >full text of the license. I saw some other projects put both headers in a file with mixed content. I don't think it is worth trying to find every instance of mixed content in our releases, but for Matrix and FlatUI it could make sense. What are your thoughts on that? > >For FalconJX: > >Seems odd to me that we have code by Robert Penner and Grant Skinner in >the source release but only the binary release LICENSE mentions that. I >know they are patch files but the I'd add them to the LICENSE file to be >on the safe side. At worse case that’s just a documentation issue, but >not having them in the source LICENSE could be a licensing error. I don't know what lawyers would say, but IMO, a patch belongs to the person doing the modifications. Otherwise, we'd get into some weird nit-picking if someone submitted a patch where they deleted an unnecessary line of code, we would say they didn't own the modification since all content in the patch file would be stuff authored by others. > >Would be nice to see a bit more info in release notes to what has changed >since the last version, I think users would want to know what changed in >a bit more detail from the last release. Looks like we're not going to cut an RC until Om fixes NPM so anyone who has time to add more details is welcome to do so. > >We not making a release of Falcon right, just FalconJX? Correct -Alex
AW: Will we have a new release out the door till 8th of September?
But in jest to release Maven stuff we need a release of falcon to. I dud two-factor quit a lot of the structure there and falcon an falconjx are both part of the same Maven build. Is there a reason for not releasing everything? Chris Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Alex Harui Datum: 20.08.16 08:59 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: Will we have a new release out the door till 8th of September? Thanks for the timely review. On 8/19/16, 4:58 PM, "Justin Mclean" wrote: >Hi, > >For FlexJS: > >I can see that mention of OpenFL has been added to LICENSE, however the >file in question [1] has an Apache license header (not MIT as I think it >should be). We’re also not following the terms of it's MIT license [2] to >include the copyright and full text of the license. Usually you add that >as a pointer to the license file in the LICENSE [3] and / or leave the >full text in the header. > >We also have the same issue with Flat UI i.e. missing the copyright and >full text of the license. I saw some other projects put both headers in a file with mixed content. I don't think it is worth trying to find every instance of mixed content in our releases, but for Matrix and FlatUI it could make sense. What are your thoughts on that? > >For FalconJX: > >Seems odd to me that we have code by Robert Penner and Grant Skinner in >the source release but only the binary release LICENSE mentions that. I >know they are patch files but the I'd add them to the LICENSE file to be >on the safe side. At worse case that’s just a documentation issue, but >not having them in the source LICENSE could be a licensing error. I don't know what lawyers would say, but IMO, a patch belongs to the person doing the modifications. Otherwise, we'd get into some weird nit-picking if someone submitted a patch where they deleted an unnecessary line of code, we would say they didn't own the modification since all content in the patch file would be stuff authored by others. > >Would be nice to see a bit more info in release notes to what has changed >since the last version, I think users would want to know what changed in >a bit more detail from the last release. Looks like we're not going to cut an RC until Om fixes NPM so anyone who has time to add more details is welcome to do so. > >We not making a release of Falcon right, just FalconJX? Correct -Alex
Re: AW: Will we have a new release out the door till 8th of September?
CI Builds seem to have created something: flex-falcon (only the apache-flex-falconjx files): http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon%20release%20branch /lastSuccessfulBuild/artifact/out/ flex-asjs: http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs_release_branch/lastS uccessfulBuild/artifact/out/ -Alex On 8/19/16, 9:56 AM, "Alex Harui" wrote: > > >On 8/19/16, 8:50 AM, "Christofer Dutz" wrote: > >>Ok so if we are all set and ready, I would start preparing a 1.0.0 >>release of burg-types and the build tools plugin and then stage a Maven >>release (candidate) in a staffing repo. As soon as that's done, one of >>you could initiate a normal ant release build. >> >>Are you ok with that? > >I think you can definitely start on the process. I doubt any of the files >involved in that area will change. Hopefully Justin will report in soon. > >-Alex >
Re: AW: Will we have a new release out the door till 8th of September?
On 8/19/16, 8:50 AM, "Christofer Dutz" wrote: >Ok so if we are all set and ready, I would start preparing a 1.0.0 >release of burg-types and the build tools plugin and then stage a Maven >release (candidate) in a staffing repo. As soon as that's done, one of >you could initiate a normal ant release build. > >Are you ok with that? I think you can definitely start on the process. I doubt any of the files involved in that area will change. Hopefully Justin will report in soon. -Alex
AW: Will we have a new release out the door till 8th of September?
Ok so if we are all set and ready, I would start preparing a 1.0.0 release of burg-types and the build tools plugin and then stage a Maven release (candidate) in a staffing repo. As soon as that's done, one of you could initiate a normal ant release build. Are you ok with that? Chris Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Josh Tynjala Datum: 19.08.16 16:28 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: Will we have a new release out the door till 8th of September? I have been using the latest nightlies to work on some projects, and things look good to me. - Josh On Fri, Aug 19, 2016 at 7:06 AM, Alex Harui wrote: > > > On 8/19/16, 1:41 AM, "Justin Mclean" wrote: > > >Hi, > > > >> Should we wait for more reviews or create release candidates? > > > >IMO proof is in the eating rather than looking at the menu, time for a RC! > > I'm not sure what that means, but I believe it has been agreed upon that > we are supposed to conduct as thorough a review of the nightly builds as > would be done of the RC, because it is way more efficient to find a > problem in the nightly than in the RC. Even the board has recommended > such an approach, and for reviewing commits. > > So please, make a review of the latest nightly or of the commits since > your last review of the nightly and let us know what you find. > > Thanks, > -Alex > >
AW: Will we have a new release out the door till 8th of September?
Hi Alex, the source package we should vote on will be the Ant one. That's the reason for me preparing a Maven release before the Ant. This way you can checkout the Released version (with release versions in the poms). Perhaps it would be a good idea to start with release branches this time. Chris Von: Alex Harui Gesendet: Donnerstag, 18. August 2016 16:56:46 An: dev@flex.apache.org Betreff: Re: Will we have a new release out the door till 8th of September? On 8/18/16, 4:40 AM, "Christofer Dutz" wrote: >Hi, > > >as I mentioned a few days ago, I will be having a talk on FlexJS in >Hamburg on 08.09.2016 (http://programmplaner.solutions.hamburg/#/). > > >I hope we will be able to ship a new version with the Maven support till >then? Do you think that's possible? What are we missing? > > >I would suggest that I stage a Maven release and you do an Ant release >based on the Maven Release Tag. Maven does two commits during a release: >1. change the version number to the release version, 2. Change the >version to the next development version. It tags the commit number 1 >automatically. So if you would do an Ant release from that state, the >version number should be consistent. The only thing we would need to do >is merge both ends back together, but that shouldn't be an issue as the >files touched during an Ant release should be different than those of a >Maven release. > > >The only thing I would need to do before that, would be to prepare 1.0.0 >releases of the build-helper-maven plugin and the little jburg-types jar. >I could initiate this any time. I asked this in a different thread, but where is the source package for the official vote? From the Ant or Maven builds? I have not checked the Maven builds. If the plan is to use the Ant builds for the source package, then your plan sounds fine to me. AFAIK, I am just waiting on one more check-in from Peter on the examples. It would be great to get Justin's thumbs up before starting the vote, or we can just gamble that we've addressed all of his earlier issues. Thoughts? -Alex
