Roman, If possible, I wouldn't mind observing your review.
-=e On Thu, Sep 22, 2016 at 11:14 AM, Ed Espino <esp...@apache.org> wrote: > All outstanding Apache HAWQ 2.0.0.0-incubating RC3 issues have been > resolved. We can go for RC4 as soon as possible. > > -=e > > On Thu, Sep 22, 2016 at 11:03 AM, Vineet Goel <vvin...@apache.org> wrote: > >> Seems like the pending issues are resolved, so we're good to go with RC4 >> now. >> >> Ed - would u agree? >> >> >> >> On Thu, Sep 22, 2016 at 10:23 AM Goden Yao <goden...@apache.org> wrote: >> >>> I want to check if the community thinks we're ready to spin up another >>> RC4 >>> voting. >>> Let me know so I can prepare the binary. >>> -Goden >>> >>> On Wed, Sep 21, 2016 at 6:59 AM Goden Yao <goden...@apache.org> wrote: >>> >>> > Just to confirm based on Legal-79, ppport.h is an exception with your >>> PR, >>> > it looks we're good now. >>> > Thanks Ed. >>> > -Goden >>> > >>> > >>> > On Wed, Sep 21, 2016 at 1:52 AM Ed Espino <esp...@apache.org> wrote: >>> > >>> >> FYI: the two issues related to the Perl Artistic License have been >>> >> resolved >>> >> in both 2.0.0.0-incubating and master branches: >>> >> >>> >> Remove ASF Category X incompatible JSON Perl Module (Artistic license) >>> >> https://issues.apache.org/jira/browse/HAWQ-1062 >>> >> >>> >> Declare PL/Perl's ppport.h source file to be an Artistic License >>> >> exception. >>> >> https://issues.apache.org/jira/browse/HAWQ-1065 >>> >> >>> >> On Tue, Sep 20, 2016 at 8:11 AM, Roman Shaposhnik < >>> ro...@shaposhnik.org> >>> >> wrote: >>> >> >>> >> > On Tue, Sep 20, 2016 at 2:47 AM, Ed Espino <esp...@apache.org> >>> wrote: >>> >> > > I have been reviewing the licensing of ppport.h. It is generated >>> >> header >>> >> > > file from Devel::PPPort - Perl/Pollution/Portability ( >>> >> > > http://search.cpan.org/~wolfsage/Devel-PPPort-3.32/PPPort.pm). >>> The >>> >> file >>> >> > > came to us from the original PostgreSQL source code base. >>> >> Interestingly, >>> >> > > there is this note on the project page: >>> >> > > >>> >> > > How to use ppport.h >>> >> > > >>> >> > > Don't direct the users of your module to download Devel::PPPort. >>> They >>> >> are >>> >> > > most probably no XS writers. Also, don't make ppport.h optional. >>> >> Rather, >>> >> > > just take the most recent copy of ppport.h that you can find >>> (e.g. by >>> >> > > generating it with the latest Devel::PPPort release from CPAN), >>> copy >>> >> it >>> >> > > into your project, adjust your project to use it, and distribute >>> the >>> >> > header >>> >> > > along with your module. >>> >> > > >>> >> > > >>> >> > > Is it possible this file can be an exception under the following >>> jira: >>> >> > > https://issues.apache.org/jira/browse/LEGAL-79? >>> >> > > >>> >> > > I also noticed the Apache HTTP Request Library ( >>> >> > > http://httpd.apache.org/apreq) project also ships with it's own >>> >> ppport.h >>> >> > > file generated in a similar way ( >>> >> > > >>> >> https://github.com/apache/apreq/blob/trunk/glue/perl/xsbuild >>> er/ppport.h >>> >> > ). >>> >> > > >>> >> > > @Roman or @Justin, can you provide some guidance on how to proceed >>> >> with >>> >> > > this file? >>> >> > >>> >> > See my suggestion above. On top of that, the podling needs to decide >>> >> > whether >>> >> > bundling Artistic/Perl code into its code base is so important that >>> we >>> >> > need to >>> >> > spin ASF legal wheels in motion and ask for a formal classification >>> of >>> >> the >>> >> > Artistic/Perl license. >>> >> > >>> >> > Thanks, >>> >> > Roman. >>> >> > >>> >> >>> >> >>> >> >>> >> -- >>> >> *Ed Espino* >>> >> *esp...@apache.org <esp...@apache.org>* >>> >> >>> > >>> >> > > > -- > *Ed Espino* > > > > *esp...@apache.org-- <esp...@apache.org> <esp...@apache.org> > <esp...@apache.org> <esp...@apache.org> <esp...@apache.org> > <esp...@apache.org>Ed Espino <esp...@apache.org> > <esp...@apache.org>esp...@apache.org <esp...@apache.org> * >
