Re: [VOTE] Release of Apache Falcon 0.11 RC3

2018-03-09 Thread amareshwarisr .
-0 (binding) + Signature : good + Checksums : good + LICENSE and NOTICE : good + Build : OK Seeing following jar files bundled in source code : ./unit/src/test/resources/falcon-extensions-0.11-tests.jar So, not voting a +1 because of the above issue. Thanks Amareshwari On Wed, Mar 7, 2018 at

Re: [VOTE] Release of Apache Falcon 0.9 RC0

2016-02-11 Thread amareshwarisr .
+1 (Binding) + Verified Signature + Verified Checksums + Do not see any License issues Might want to fix the year in NOTICE file to 2016 in next release :NOTICE.txt:Copyright 2011-2015 The Apache Software Foundation + Finally, Build passed for me, with out any issues Thanks Amareshwari On Tue

Re: [VOTE] Release of Apache Falcon 0.6.1 - RC2

2015-06-19 Thread amareshwarisr .
+1 Verified - signature and checksums. License and Notice - look fine. Some minor issues listed below - can be fixed in next release. Build is fine - but couple of tests failed as noted in other vote. Running mvn clean install -fae went through with two test failures. Thanks Shaik for driving it

Re: [CANCEL] [VOTE] Release of Apache Falcon 0.6.1 - RC1

2015-06-16 Thread amareshwarisr .
ase of Apache Falcon 0.6.1 - RC1 > To: dev@falcon.apache.org > > > Amareshwari, > The test failures are probably caused by this - > https://issues.apache.org/jira/browse/FALCON-1203 > > Regards, > Pallavi > > On Tue, Jun 16, 2015 at 2:49 PM, amares

Re: [VOTE] Release of Apache Falcon 0.6.1 - RC1

2015-06-16 Thread amareshwarisr .
+0 Verified : Checksums : Good Signature : Good Licensing : Found some issues with Jasmine license. Notice : Year should be changed to 2015. Jasmine license contains the text for http://angularjs.org : Where as they actually have copyright from Pivotal Labs : ./falcon-ui/app/test/lib/jas

Re: [DRAFT] Board report for June 2015

2015-06-09 Thread amareshwarisr .
Missing link? On Wed, Jun 10, 2015 at 11:03 AM, Srikanth Sundarrajan wrote: > Hi All, > Board report is due this month for Apache Falcon. Please find draft > version here. Please provide your inputs on the report. > > Regards > Srikanth Sundarrajan >

Re: [VOTE] Release of Apache Falcon 0.6.1 - RC0

2015-05-12 Thread amareshwarisr .
-ui/img/falcon.xcf has " Copyright (c) 1998 Hewlett-Packard Company " falcon-ui/node_modules/protractor/node_modules/selenium-webdriver/lib/test/data/beach.jpg has Copyright 2003 Apple Computer Inc., all rights reserved Thanks Amareshwari On Tue, May 12, 2015 at 1:23 PM, amareshwaris

Re: [VOTE] Release of Apache Falcon 0.6.1 - RC0

2015-05-12 Thread amareshwarisr .
I was not sure if node_modules was part of this release only or was part of earlier releases also. Just got confirmation that they are introduced in this release. Changing my vote to -1 for licensing issues. Thanks Amareshwari On Tue, May 12, 2015 at 12:46 PM, amareshwarisr . wrote: > 0 (

Re: [VOTE] Release of Apache Falcon 0.6.1 - RC0

2015-05-12 Thread amareshwarisr .
0 (i'm facing build issues for building from source). - Signature looks good - Verified md5 checksum - Could not verify sha as i see the contents of apache-falcon-0.6.1-sources.tar.gz.sha as binary . - Saw some binary files, not sure if there was already any discussion regarding

Re: Did you know this....

2015-01-19 Thread amareshwarisr .
Really great job! On Tue, Jan 20, 2015 at 12:19 PM, Ajay Yadav wrote: > This is fantastic! We should probably add Expedia to the list of powered by > Falcon :) > > On Tue, Jan 20, 2015 at 11:50 AM, Jean-Baptiste Onofré > wrote: > >

Re: Back in the business, user mailing list ?

2015-01-13 Thread amareshwarisr .
Some thoughts on user mailing list : Trying to put what should go in user mailing list and what not (started doing this nowdays) What should go - A question from user - regarding usage? - Announcements to users - new feature/new release and etc. - Not sure people will only subscribe to

Re: [DISCUSS] Alternative flow for committing patches

2015-01-09 Thread amareshwarisr .
Very nice. I really liked it. Can we pass a reviewer name to -s as well, to say signed off by someone else? I see main challenge will be with contributor who didn't follow the patch generation with format patch/squashing/commit messages. For such patches fall back to old style? Thanks Amareshwar