Re: [VOTE] MADlib v1.10-rc1

[Frank McQuillan]

To finish this thread, I captured all of these licensing issues on the
MADlib wiki at
https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance
should anyone need to refer to it.


On Tue, Feb 28, 2017 at 11:43 AM, Frank McQuillan 
wrote:

> Thanks Rahul.  I see your commit has addressed the remaining issues:
> https://git1-us-west.apache.org/repos/asf?p=incubator-
> madlib.git;a=commit;h=a3863b6c
>
> We are declaring create_indicators.* as new files so they will have
> Apache header.
>
> For the record, I attached an Excel spreadsheet with some more notes so
> that we remember how we went from the two lists Rahul posted above to the
> above commit.
>
> Frank
>
> On Mon, Feb 27, 2017 at 5:44 PM, Rahul Iyer  wrote:
>
>> I have attached two files:
>>
>> new_files_after_apache.txt: New files added since September 15, 2015
>> (grant date) till date
>> files_w_apache_header.txt: Files that contain the Apache header right
>> now.
>>
>> Comparing the two lists, there are open questions regarding below files.
>>
>> Extra headers:
>> - sort-module.py has Apache header but was created before grant (recently
>> edited and header added). *I'll fix this*.
>> - create_indicators.* have headers but were renamed from
>> data_preparation.*. *What is the legal guidance with this*?
>>
>> No header:
>> - class_diagram.mp looks like a text file with no header, even though it
>> was added just after the grant. I'm not aware of the purpose of this file.
>>
>>
>>
>> On Mon, Feb 27, 2017 at 4:42 PM, Frank McQuillan 
>> wrote:
>>
>>> OK, so we need to go back and do the comparison from the original code
>>> grant in the fall of 2015 to the  current 1.10 release candidate.
>>>
>>> On Mon, Feb 27, 2017 at 4:19 PM, Roman Shaposhnik 
>>> wrote:
>>>
>>> > Frank, I'm not sure I understand the question. The criteria needs to
>>> hold
>>> > for anything that came in via the initial code ingest compared to how
>>> the
>>> > master of your project looks now.
>>> >
>>> > Thanks,
>>> > Roman.
>>> >
>>> > On Mon, Feb 27, 2017 at 4:10 PM, Frank McQuillan <
>>> fmcquil...@pivotal.io>
>>> > wrote:
>>> > > Roman,
>>> > >
>>> > > Does this apply retro-actively back to initial grant of the code to
>>> > ASF?  Or
>>> > > just from the last release 1.9.1?
>>> > >
>>> > > Frank
>>> > >
>>> > > On Sun, Feb 26, 2017 at 11:23 PM, Roman Shaposhnik <
>>> ro...@shaposhnik.org
>>> > >
>>> > > wrote:
>>> > >>
>>> > >> Here's the ultimate resolution on the IP issue:
>>> > >>* we don't do anything with existing (BSD) files even if we edit
>>> them
>>> > >>* every new file we create gets an ASF license header
>>> > >>
>>> > >> More details:
>>> > >>
>>> > >> https://issues.apache.org/jira/browse/LEGAL-293?
>>> > focusedCommentId=15881595=com.atlassian.jira.
>>> > plugin.system.issuetabpanels:comment-tabpanel#comment-15881595
>>> > >>
>>> > >> Thanks,
>>> > >> Roman.
>>> > >>
>>> > >> On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan <
>>> fmcquil...@pivotal.io
>>> > >
>>> > >> wrote:
>>> > >> > Thanks Roman for working on this.
>>> > >> >
>>> > >> > If you feel a final answer will be ready next week, then yes by
>>> all
>>> > >> > means l
>>> > >> > would suggest to the community that we wait and re-spin an RC2
>>> with
>>> > the
>>> > >> > license headers issue resolved.  Seems less overhead and effort
>>> than a
>>> > >> > quick follow on release right after 1.10.  Also, there some
>>> momentum
>>> > >> > going
>>> > >> > with the legal discussion, so let's take advantage of that.
>>> > >> >
>>> > >> > Satoshi (release manager), are you OK pausing the RC2 until we
>>> hear
>>> > back
>>> > >> > from Roman next week?
>>> > >> >
>>> > >> > Thank you,
>>> > >> > Frank
>>> > >> >
>>> > >> >
>>> > >> > On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik <
>>> > ro...@shaposhnik.org>
>>> > >> > wrote:
>>> > >> >
>>> > >> >> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan
>>> > >> >> 
>>> > >> >> wrote:
>>> > >> >> > Agree with Rahul re putting up an RC2 with the suggested
>>> changes
>>> > from
>>> > >> >> Roman,
>>> > >> >> > including incorporating Ed's comments on copyright year and top
>>> > level
>>> > >> >> folder
>>> > >> >> > naming.  These are really items but let's respond to the RC1
>>> > >> >> > reviewers
>>> > >> >> the
>>> > >> >> > best way we can.
>>> > >> >>
>>> > >> >> +1 to a respin.
>>> > >> >>
>>> > >> >> > Regarding the ASF legal issue being discussed, MADLib
>>> community is
>>> > >> >> > more
>>> > >> >> than
>>> > >> >> > happy to respond to any guidance from the fine folks at the ASF
>>> > >> >> > around
>>> > >> >> > headers with appropriate licensing verbage.  We just need to
>>> know
>>> > >> >> > what
>>> > >> >> that
>>> > >> >> > guidance is.
>>> > >> >>
>>> > >> >> Well, if you're ok respinning next week I hope to get you a final
>>> > >> >> answer by then.
>>> > >> >> Might as well kill two birds with 

Re: [VOTE] MADlib v1.10-rc1

[Frank McQuillan]

Thanks Rahul.  I see your commit has addressed the remaining issues:
https://git1-us-west.apache.org/repos/asf?p=incubator-madlib.git;a=commit;h=a3863b6c

We are declaring create_indicators.* as new files so they will have Apache
header.

For the record, I attached an Excel spreadsheet with some more notes so
that we remember how we went from the two lists Rahul posted above to the
above commit.

Frank

On Mon, Feb 27, 2017 at 5:44 PM, Rahul Iyer  wrote:

> I have attached two files:
>
> new_files_after_apache.txt: New files added since September 15, 2015
> (grant date) till date
> files_w_apache_header.txt: Files that contain the Apache header right now.
>
> Comparing the two lists, there are open questions regarding below files.
>
> Extra headers:
> - sort-module.py has Apache header but was created before grant (recently
> edited and header added). *I'll fix this*.
> - create_indicators.* have headers but were renamed from
> data_preparation.*. *What is the legal guidance with this*?
>
> No header:
> - class_diagram.mp looks like a text file with no header, even though it
> was added just after the grant. I'm not aware of the purpose of this file.
>
>
>
> On Mon, Feb 27, 2017 at 4:42 PM, Frank McQuillan 
> wrote:
>
>> OK, so we need to go back and do the comparison from the original code
>> grant in the fall of 2015 to the  current 1.10 release candidate.
>>
>> On Mon, Feb 27, 2017 at 4:19 PM, Roman Shaposhnik 
>> wrote:
>>
>> > Frank, I'm not sure I understand the question. The criteria needs to
>> hold
>> > for anything that came in via the initial code ingest compared to how
>> the
>> > master of your project looks now.
>> >
>> > Thanks,
>> > Roman.
>> >
>> > On Mon, Feb 27, 2017 at 4:10 PM, Frank McQuillan > >
>> > wrote:
>> > > Roman,
>> > >
>> > > Does this apply retro-actively back to initial grant of the code to
>> > ASF?  Or
>> > > just from the last release 1.9.1?
>> > >
>> > > Frank
>> > >
>> > > On Sun, Feb 26, 2017 at 11:23 PM, Roman Shaposhnik <
>> ro...@shaposhnik.org
>> > >
>> > > wrote:
>> > >>
>> > >> Here's the ultimate resolution on the IP issue:
>> > >>* we don't do anything with existing (BSD) files even if we edit
>> them
>> > >>* every new file we create gets an ASF license header
>> > >>
>> > >> More details:
>> > >>
>> > >> https://issues.apache.org/jira/browse/LEGAL-293?
>> > focusedCommentId=15881595=com.atlassian.jira.
>> > plugin.system.issuetabpanels:comment-tabpanel#comment-15881595
>> > >>
>> > >> Thanks,
>> > >> Roman.
>> > >>
>> > >> On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan <
>> fmcquil...@pivotal.io
>> > >
>> > >> wrote:
>> > >> > Thanks Roman for working on this.
>> > >> >
>> > >> > If you feel a final answer will be ready next week, then yes by all
>> > >> > means l
>> > >> > would suggest to the community that we wait and re-spin an RC2 with
>> > the
>> > >> > license headers issue resolved.  Seems less overhead and effort
>> than a
>> > >> > quick follow on release right after 1.10.  Also, there some
>> momentum
>> > >> > going
>> > >> > with the legal discussion, so let's take advantage of that.
>> > >> >
>> > >> > Satoshi (release manager), are you OK pausing the RC2 until we hear
>> > back
>> > >> > from Roman next week?
>> > >> >
>> > >> > Thank you,
>> > >> > Frank
>> > >> >
>> > >> >
>> > >> > On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik <
>> > ro...@shaposhnik.org>
>> > >> > wrote:
>> > >> >
>> > >> >> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan
>> > >> >> 
>> > >> >> wrote:
>> > >> >> > Agree with Rahul re putting up an RC2 with the suggested changes
>> > from
>> > >> >> Roman,
>> > >> >> > including incorporating Ed's comments on copyright year and top
>> > level
>> > >> >> folder
>> > >> >> > naming.  These are really items but let's respond to the RC1
>> > >> >> > reviewers
>> > >> >> the
>> > >> >> > best way we can.
>> > >> >>
>> > >> >> +1 to a respin.
>> > >> >>
>> > >> >> > Regarding the ASF legal issue being discussed, MADLib community
>> is
>> > >> >> > more
>> > >> >> than
>> > >> >> > happy to respond to any guidance from the fine folks at the ASF
>> > >> >> > around
>> > >> >> > headers with appropriate licensing verbage.  We just need to
>> know
>> > >> >> > what
>> > >> >> that
>> > >> >> > guidance is.
>> > >> >>
>> > >> >> Well, if you're ok respinning next week I hope to get you a final
>> > >> >> answer by then.
>> > >> >> Might as well kill two birds with the same RC. Or we can quickly
>> do a
>> > >> >> follow up
>> > >> >> release once the licensing headers dust settles. Up to you guys.
>> > >> >>
>> > >> >> Thanks,
>> > >> >> Roman.
>> > >> >>
>> > >
>> > >
>> >
>>
>
>


file headers work1.xlsx
Description: MS-Excel 2007 spreadsheet

Re: [VOTE] MADlib v1.10-rc1

[Rahul Iyer]

I have attached two files:

new_files_after_apache.txt: New files added since September 15, 2015 (grant
date) till date
files_w_apache_header.txt: Files that contain the Apache header right now.

Comparing the two lists, there are open questions regarding below files.

Extra headers:
- sort-module.py has Apache header but was created before grant (recently
edited and header added). *I'll fix this*.
- create_indicators.* have headers but were renamed from
data_preparation.*. *What is the legal guidance with this*?

No header:
- class_diagram.mp looks like a text file with no header, even though it
was added just after the grant. I'm not aware of the purpose of this file.



On Mon, Feb 27, 2017 at 4:42 PM, Frank McQuillan 
wrote:

> OK, so we need to go back and do the comparison from the original code
> grant in the fall of 2015 to the  current 1.10 release candidate.
>
> On Mon, Feb 27, 2017 at 4:19 PM, Roman Shaposhnik 
> wrote:
>
> > Frank, I'm not sure I understand the question. The criteria needs to hold
> > for anything that came in via the initial code ingest compared to how the
> > master of your project looks now.
> >
> > Thanks,
> > Roman.
> >
> > On Mon, Feb 27, 2017 at 4:10 PM, Frank McQuillan 
> > wrote:
> > > Roman,
> > >
> > > Does this apply retro-actively back to initial grant of the code to
> > ASF?  Or
> > > just from the last release 1.9.1?
> > >
> > > Frank
> > >
> > > On Sun, Feb 26, 2017 at 11:23 PM, Roman Shaposhnik <
> ro...@shaposhnik.org
> > >
> > > wrote:
> > >>
> > >> Here's the ultimate resolution on the IP issue:
> > >>* we don't do anything with existing (BSD) files even if we edit
> them
> > >>* every new file we create gets an ASF license header
> > >>
> > >> More details:
> > >>
> > >> https://issues.apache.org/jira/browse/LEGAL-293?
> > focusedCommentId=15881595=com.atlassian.jira.
> > plugin.system.issuetabpanels:comment-tabpanel#comment-15881595
> > >>
> > >> Thanks,
> > >> Roman.
> > >>
> > >> On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan <
> fmcquil...@pivotal.io
> > >
> > >> wrote:
> > >> > Thanks Roman for working on this.
> > >> >
> > >> > If you feel a final answer will be ready next week, then yes by all
> > >> > means l
> > >> > would suggest to the community that we wait and re-spin an RC2 with
> > the
> > >> > license headers issue resolved.  Seems less overhead and effort
> than a
> > >> > quick follow on release right after 1.10.  Also, there some momentum
> > >> > going
> > >> > with the legal discussion, so let's take advantage of that.
> > >> >
> > >> > Satoshi (release manager), are you OK pausing the RC2 until we hear
> > back
> > >> > from Roman next week?
> > >> >
> > >> > Thank you,
> > >> > Frank
> > >> >
> > >> >
> > >> > On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik <
> > ro...@shaposhnik.org>
> > >> > wrote:
> > >> >
> > >> >> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan
> > >> >> 
> > >> >> wrote:
> > >> >> > Agree with Rahul re putting up an RC2 with the suggested changes
> > from
> > >> >> Roman,
> > >> >> > including incorporating Ed's comments on copyright year and top
> > level
> > >> >> folder
> > >> >> > naming.  These are really items but let's respond to the RC1
> > >> >> > reviewers
> > >> >> the
> > >> >> > best way we can.
> > >> >>
> > >> >> +1 to a respin.
> > >> >>
> > >> >> > Regarding the ASF legal issue being discussed, MADLib community
> is
> > >> >> > more
> > >> >> than
> > >> >> > happy to respond to any guidance from the fine folks at the ASF
> > >> >> > around
> > >> >> > headers with appropriate licensing verbage.  We just need to know
> > >> >> > what
> > >> >> that
> > >> >> > guidance is.
> > >> >>
> > >> >> Well, if you're ok respinning next week I hope to get you a final
> > >> >> answer by then.
> > >> >> Might as well kill two birds with the same RC. Or we can quickly
> do a
> > >> >> follow up
> > >> >> release once the licensing headers dust settles. Up to you guys.
> > >> >>
> > >> >> Thanks,
> > >> >> Roman.
> > >> >>
> > >
> > >
> >
>
pom.xml
examples/hello_world/iterative/simple_logistic.cpp
examples/hello_world/iterative/simple_logistic.hpp
examples/hello_world/iterative/simple_logistic.py_in
examples/hello_world/non-iterative/avg_var.cpp
examples/hello_world/iterative/simple_logistic.sql_in
examples/hello_world/non-iterative/avg_var.hpp
examples/hello_world/non-iterative/avg_var.sql_in
src/madpack/changelist_1.8_1.10.yaml
src/madpack/changelist_1.9_1.10.yaml
src/madpack/sort-module.py
doc/design/modules/graph.tex
src/modules/utilities/path.cpp
src/modules/utilities/path.hpp
methods/stemmer/src/pg_gp/porter_stemmer.c
src/modules/utilities/utilities.hpp
methods/stemmer/src/pg_gp/porter_stemmer.sql_in
src/ports/greenplum/5/CMakeLists.txt
src/ports/greenplum/cmake/FindGreenplum_5.cmake
src/ports/hawq/2/CMakeLists.txt
src/ports/hawq/cmake/FindHAWQ_2.cmake
src/ports/postgres/9.5/CMakeLists.txt

Re: [VOTE] MADlib v1.10-rc1

[Roman Shaposhnik]

Frank, I'm not sure I understand the question. The criteria needs to hold
for anything that came in via the initial code ingest compared to how the
master of your project looks now.

Thanks,
Roman.

On Mon, Feb 27, 2017 at 4:10 PM, Frank McQuillan  wrote:
> Roman,
>
> Does this apply retro-actively back to initial grant of the code to ASF?  Or
> just from the last release 1.9.1?
>
> Frank
>
> On Sun, Feb 26, 2017 at 11:23 PM, Roman Shaposhnik 
> wrote:
>>
>> Here's the ultimate resolution on the IP issue:
>>* we don't do anything with existing (BSD) files even if we edit them
>>* every new file we create gets an ASF license header
>>
>> More details:
>>
>> https://issues.apache.org/jira/browse/LEGAL-293?focusedCommentId=15881595=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15881595
>>
>> Thanks,
>> Roman.
>>
>> On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan 
>> wrote:
>> > Thanks Roman for working on this.
>> >
>> > If you feel a final answer will be ready next week, then yes by all
>> > means l
>> > would suggest to the community that we wait and re-spin an RC2 with the
>> > license headers issue resolved.  Seems less overhead and effort than a
>> > quick follow on release right after 1.10.  Also, there some momentum
>> > going
>> > with the legal discussion, so let's take advantage of that.
>> >
>> > Satoshi (release manager), are you OK pausing the RC2 until we hear back
>> > from Roman next week?
>> >
>> > Thank you,
>> > Frank
>> >
>> >
>> > On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik 
>> > wrote:
>> >
>> >> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan
>> >> 
>> >> wrote:
>> >> > Agree with Rahul re putting up an RC2 with the suggested changes from
>> >> Roman,
>> >> > including incorporating Ed's comments on copyright year and top level
>> >> folder
>> >> > naming.  These are really items but let's respond to the RC1
>> >> > reviewers
>> >> the
>> >> > best way we can.
>> >>
>> >> +1 to a respin.
>> >>
>> >> > Regarding the ASF legal issue being discussed, MADLib community is
>> >> > more
>> >> than
>> >> > happy to respond to any guidance from the fine folks at the ASF
>> >> > around
>> >> > headers with appropriate licensing verbage.  We just need to know
>> >> > what
>> >> that
>> >> > guidance is.
>> >>
>> >> Well, if you're ok respinning next week I hope to get you a final
>> >> answer by then.
>> >> Might as well kill two birds with the same RC. Or we can quickly do a
>> >> follow up
>> >> release once the licensing headers dust settles. Up to you guys.
>> >>
>> >> Thanks,
>> >> Roman.
>> >>
>
>

Re: [VOTE] MADlib v1.10-rc1

[Frank McQuillan]

Roman,

Does this apply retro-actively back to initial grant of the code to ASF?
Or just from the last release 1.9.1?

Frank

On Sun, Feb 26, 2017 at 11:23 PM, Roman Shaposhnik 
wrote:

> Here's the ultimate resolution on the IP issue:
>* we don't do anything with existing (BSD) files even if we edit them
>* every new file we create gets an ASF license header
>
> More details:
>https://issues.apache.org/jira/browse/LEGAL-293?
> focusedCommentId=15881595=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-15881595
>
> Thanks,
> Roman.
>
> On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan 
> wrote:
> > Thanks Roman for working on this.
> >
> > If you feel a final answer will be ready next week, then yes by all
> means l
> > would suggest to the community that we wait and re-spin an RC2 with the
> > license headers issue resolved.  Seems less overhead and effort than a
> > quick follow on release right after 1.10.  Also, there some momentum
> going
> > with the legal discussion, so let's take advantage of that.
> >
> > Satoshi (release manager), are you OK pausing the RC2 until we hear back
> > from Roman next week?
> >
> > Thank you,
> > Frank
> >
> >
> > On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik 
> > wrote:
> >
> >> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan  >
> >> wrote:
> >> > Agree with Rahul re putting up an RC2 with the suggested changes from
> >> Roman,
> >> > including incorporating Ed's comments on copyright year and top level
> >> folder
> >> > naming.  These are really items but let's respond to the RC1 reviewers
> >> the
> >> > best way we can.
> >>
> >> +1 to a respin.
> >>
> >> > Regarding the ASF legal issue being discussed, MADLib community is
> more
> >> than
> >> > happy to respond to any guidance from the fine folks at the ASF around
> >> > headers with appropriate licensing verbage.  We just need to know what
> >> that
> >> > guidance is.
> >>
> >> Well, if you're ok respinning next week I hope to get you a final
> >> answer by then.
> >> Might as well kill two birds with the same RC. Or we can quickly do a
> >> follow up
> >> release once the licensing headers dust settles. Up to you guys.
> >>
> >> Thanks,
> >> Roman.
> >>
>

Re: [VOTE] MADlib v1.10-rc1

[Roman Shaposhnik]

Here's the ultimate resolution on the IP issue:
   * we don't do anything with existing (BSD) files even if we edit them
   * every new file we create gets an ASF license header

More details:
   
https://issues.apache.org/jira/browse/LEGAL-293?focusedCommentId=15881595=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15881595

Thanks,
Roman.

On Tue, Feb 21, 2017 at 5:54 PM, Frank McQuillan  wrote:
> Thanks Roman for working on this.
>
> If you feel a final answer will be ready next week, then yes by all means l
> would suggest to the community that we wait and re-spin an RC2 with the
> license headers issue resolved.  Seems less overhead and effort than a
> quick follow on release right after 1.10.  Also, there some momentum going
> with the legal discussion, so let's take advantage of that.
>
> Satoshi (release manager), are you OK pausing the RC2 until we hear back
> from Roman next week?
>
> Thank you,
> Frank
>
>
> On Tue, Feb 21, 2017 at 4:45 PM, Roman Shaposhnik 
> wrote:
>
>> On Tue, Feb 21, 2017 at 2:55 PM, Frank McQuillan 
>> wrote:
>> > Agree with Rahul re putting up an RC2 with the suggested changes from
>> Roman,
>> > including incorporating Ed's comments on copyright year and top level
>> folder
>> > naming.  These are really items but let's respond to the RC1 reviewers
>> the
>> > best way we can.
>>
>> +1 to a respin.
>>
>> > Regarding the ASF legal issue being discussed, MADLib community is more
>> than
>> > happy to respond to any guidance from the fine folks at the ASF around
>> > headers with appropriate licensing verbage.  We just need to know what
>> that
>> > guidance is.
>>
>> Well, if you're ok respinning next week I hope to get you a final
>> answer by then.
>> Might as well kill two birds with the same RC. Or we can quickly do a
>> follow up
>> release once the licensing headers dust settles. Up to you guys.
>>
>> Thanks,
>> Roman.
>>

Re: [VOTE] MADlib v1.10-rc1

[Marshall Presser]

+1

On Thu, Feb 16, 2017 at 12:17 PM, Frank McQuillan 
wrote:

> +1
>
> Frank McQuillan
>
> On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu  wrote:
>
>> Hello MADlib community,
>>
>> We have created a MADlib 1.10 RC-1, with the artifacts below up for a
>> vote.
>>
>> This will be the 4th release for Apache MADlib (incubating).
>>
>> The main goals of this release are:
>> * new modules (single source shortest path for graph analytics, encode
>> categorical variables, K-nearest neighbors)
>> * improvements to existing modules (add grouping support to elastic
>> net and PCA, add cross validation to elastic net, array input for
>> K-means, verbose output option for DT and RF, limit itemset size in
>> association rules, various madpack installer improvements)
>> * platform updates (PostgreSQL 9.6)
>> * bug fixes
>> * doc improvements
>>
>> For more information including release notes, please see:
>> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
>>
>> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST ***
>>
>> We're voting upon the source (tag):  rc/1.10.0-rc1
>> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
>>
>> Source Files:
>> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.10
>> .0-incubating-rc1/
>>
>> Commit to be voted upon:
>> https://github.com/apache/incubator-madlib/commit/ea17530bfe
>> 22a1fde173d7fa83508cbcd9924c20
>>
>> KEYS file containing PGP Keys we use to sign the release:
>> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
>>
>> To help in tallying the vote, can PMC members please be sure to
>> indicate "(binding)" with their vote.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> --
>> Satoshi Nagayasu 
>>
>
>


-- 
Marshall Presser
Pivotal Data Engineering
mpresser@pivotal .io
240.401.1750

Re: [VOTE] MADlib v1.10-rc1

[Satoshi Nagayasu]

Hi,

2017-02-17 4:58 GMT+09:00 Ed Espino :
> A few MADlib v1.10-rc1 observations from a HAWQ incubator committer.
>
>- The Copyright year (2016) in the NOTICE file needs to be updated to
>2017. I believe this can be handled in next release.

I have created a pull request to fix this.
https://github.com/apache/incubator-madlib/pull/104

>- As it still applies, similar to a past comment by Roman ([VOTE] MADlib
>v1.9.1-rc2
>
> )

Here is the checklist from the previous release process:

>   * imported keys from the provided KEYS file
>   * checksums and signatures
>   * the release archive is identical to the content of the tag
>   * DICLAIMER, LICENSE and NOTICE are all as they should be

Hope these would go well. :D

>   * ran RAT check (via mvn verify) and made sure that the license
> headers in files get properly recognized and the excluded BSD
> licensed files are correctly excluded
>   * all brand new files in this release have ALv2 headers

Yes, you all can check the RAT result here (see rat.txt):
http://161.202.86.165/build/incubator-madlib/

> Minor nits that I stills strongly suggest you address in future release:
>   * name of the top level folder in the archive is weird. The usual practice
> is to call the top level folder as -

I would like to fix this as following.

>- *"* name of the top level folder in the archive is weird. The usual
>practice is to call the top level folder as -*"*
> (example: *apache-madlib-src-1.10-incubating* instead of
>*incubator-madlib*)

I would like to suggest the name of the top directory "incubator-madlib-1.10.0".

My artifacts for testing purpose are available here:
http://161.202.86.165/build/incubator-madlib/

These artifacts are generated automatically in every 3 hours with running
install-check (against PG 9.6) and Apace RAT.

>- I'm more curious than anything. Why did Orhan sign the release? I was
>expecting the release manager (Satoshi Nagayasu) to have signed the 
> release.

Right, I need Orhan's help as he mentioned in another reply.

>- Checksums and PGP signature are good.
>-  ASF headers check: I spot checked files added (git whatchanged
>--diff-filter=A) since the last release. ASF headers look good.  Nice Job!

Hope these could be ok. :D

Regards,
-- 
Satoshi Nagayasu 

Re: [VOTE] MADlib v1.10-rc1

[FENG, Xixuan (Aaron)]

+1

- Aaron

2017年2月17日(金) 3:05 Orhan Kislal :

> +1
>
> Orhan Kislal
>
> On Thu, Feb 16, 2017 at 9:23 AM, Joe Hellerstein  > wrote:
>
> +1
>
> Sent from a telephone.
>
>
>
> > On Feb 16, 2017, at 9:17 AM, Frank McQuillan 
> wrote:
> >
> > +1
> >
> > Frank McQuillan
> >
> >> On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu 
> wrote:
> >>
> >> Hello MADlib community,
> >>
> >> We have created a MADlib 1.10 RC-1, with the artifacts below up for a
> vote.
> >>
> >> This will be the 4th release for Apache MADlib (incubating).
> >>
> >> The main goals of this release are:
> >> * new modules (single source shortest path for graph analytics, encode
> >> categorical variables, K-nearest neighbors)
> >> * improvements to existing modules (add grouping support to elastic
> >> net and PCA, add cross validation to elastic net, array input for
> >> K-means, verbose output option for DT and RF, limit itemset size in
> >> association rules, various madpack installer improvements)
> >> * platform updates (PostgreSQL 9.6)
> >> * bug fixes
> >> * doc improvements
> >>
> >> For more information including release notes, please see:
> >> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
> >>
> >> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST ***
> >>
> >> We're voting upon the source (tag):  rc/1.10.0-rc1
> >> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
> >>
> >> Source Files:
> >> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.
> >> 10.0-incubating-rc1/
> >>
> >> Commit to be voted upon:
> >> https://github.com/apache/incubator-madlib/commit/
> >> ea17530bfe22a1fde173d7fa83508cbcd9924c20
> >>
> >> KEYS file containing PGP Keys we use to sign the release:
> >> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
> >>
> >> To help in tallying the vote, can PMC members please be sure to
> >> indicate "(binding)" with their vote.
> >>
> >> [ ] +1  approve
> >> [ ] +0  no opinion
> >> [ ] -1  disapprove (and reason why)
> >>
> >> --
> >> Satoshi Nagayasu 
> >>
>
>

Re: [VOTE] MADlib v1.10-rc1

[ChenLiang Wang]

+1

On 02/16/2017 11:27 AM, Satoshi Nagayasu wrote:
> Hello MADlib community,
> 
> We have created a MADlib 1.10 RC-1, with the artifacts below up for a vote.
> 
> This will be the 4th release for Apache MADlib (incubating).
> 
> The main goals of this release are:
> * new modules (single source shortest path for graph analytics, encode
> categorical variables, K-nearest neighbors)
> * improvements to existing modules (add grouping support to elastic
> net and PCA, add cross validation to elastic net, array input for
> K-means, verbose output option for DT and RF, limit itemset size in
> association rules, various madpack installer improvements)
> * platform updates (PostgreSQL 9.6)
> * bug fixes
> * doc improvements
> 
> For more information including release notes, please see:
> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
> 
> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST ***
> 
> We're voting upon the source (tag):  rc/1.10.0-rc1
> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
> 
> Source Files:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.10.0-incubating-rc1/
> 
> Commit to be voted upon:
> https://github.com/apache/incubator-madlib/commit/ea17530bfe22a1fde173d7fa83508cbcd9924c20
> 
> KEYS file containing PGP Keys we use to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
> 
> To help in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote.
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 

Re: [VOTE] MADlib v1.10-rc1

[Rahul Iyer]

+1

On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu  wrote:

> Hello MADlib community,
>
> We have created a MADlib 1.10 RC-1, with the artifacts below up for a vote.
>
> This will be the 4th release for Apache MADlib (incubating).
>
> The main goals of this release are:
> * new modules (single source shortest path for graph analytics, encode
> categorical variables, K-nearest neighbors)
> * improvements to existing modules (add grouping support to elastic
> net and PCA, add cross validation to elastic net, array input for
> K-means, verbose output option for DT and RF, limit itemset size in
> association rules, various madpack installer improvements)
> * platform updates (PostgreSQL 9.6)
> * bug fixes
> * doc improvements
>
> For more information including release notes, please see:
> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
>
> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST ***
>
> We're voting upon the source (tag):  rc/1.10.0-rc1
> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
>
> Source Files:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.
> 10.0-incubating-rc1/
>
> Commit to be voted upon:
> https://github.com/apache/incubator-madlib/commit/
> ea17530bfe22a1fde173d7fa83508cbcd9924c20
>
> KEYS file containing PGP Keys we use to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
>
> To help in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> --
> Satoshi Nagayasu 
>

Re: [VOTE] MADlib v1.10-rc1

[Ed Espino]

OK (Orhan Kislal),

Thanks for the info (Apache ID signature preferred). That will come in
handy for one of our future Apache HAWQ incubating releases.

Cheers,
-=e

On Thu, Feb 16, 2017 at 12:06 PM, Orhan Kislal  wrote:

> Hi Ed,
>
> Thanks for the review. One of the comments from the previous release was a
> preference towards a signature with an Apache id. Since Satoshi-san is not
> an Apache committer yet, I took care of the signing process.
>
> Thanks,
>
> Orhan Kislal
>
> On Thu, Feb 16, 2017 at 11:58 AM, Ed Espino  wrote:
>
> > A few MADlib v1.10-rc1 observations from a HAWQ incubator committer.
> >
> >- The Copyright year (2016) in the NOTICE file needs to be updated to
> >2017. I believe this can be handled in next release.
> >- As it still applies, similar to a past comment by Roman ([VOTE]
> MADlib
> >v1.9.1-rc2
> > > c7a78d3a9dc26bf659af94fcfe@%3Cgeneral.incubator.apache.org%3E>)
> >- *"* name of the top level folder in the archive is weird. The usual
> >practice is to call the top level folder as - > ID>*"*
> > (example: *apache-madlib-src-1.10-incubating* instead of
> >*incubator-madlib*)
> >- I'm more curious than anything. Why did Orhan sign the release? I
> was
> >expecting the release manager (Satoshi Nagayasu) to have signed the
> > release.
> >- Checksums and PGP signature are good.
> >-  ASF headers check: I spot checked files added (git whatchanged
> >--diff-filter=A) since the last release. ASF headers look good.  Nice
> > Job!
> >
> > I was going to try and build but I ran past my allotted time limit for
> this
> > review. Hopefully, I can try this soon.
> >
> > Regards,
> > -=ed espino
> >
> > On Thu, Feb 16, 2017 at 10:05 AM, Orhan Kislal 
> wrote:
> >
> > > +1
> > >
> > > Orhan Kislal
> > >
> > > On Thu, Feb 16, 2017 at 9:23 AM, Joe Hellerstein <
> > hellerst...@berkeley.edu
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Sent from a telephone.
> > > >
> > > > > On Feb 16, 2017, at 9:17 AM, Frank McQuillan <
> fmcquil...@pivotal.io>
> > > > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > Frank McQuillan
> > > > >
> > > > >> On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu <
> sn...@uptime.jp>
> > > > wrote:
> > > > >>
> > > > >> Hello MADlib community,
> > > > >>
> > > > >> We have created a MADlib 1.10 RC-1, with the artifacts below up
> for
> > a
> > > > vote.
> > > > >>
> > > > >> This will be the 4th release for Apache MADlib (incubating).
> > > > >>
> > > > >> The main goals of this release are:
> > > > >> * new modules (single source shortest path for graph analytics,
> > encode
> > > > >> categorical variables, K-nearest neighbors)
> > > > >> * improvements to existing modules (add grouping support to
> elastic
> > > > >> net and PCA, add cross validation to elastic net, array input for
> > > > >> K-means, verbose output option for DT and RF, limit itemset size
> in
> > > > >> association rules, various madpack installer improvements)
> > > > >> * platform updates (PostgreSQL 9.6)
> > > > >> * bug fixes
> > > > >> * doc improvements
> > > > >>
> > > > >> For more information including release notes, please see:
> > > > >> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
> > > > >>
> > > > >> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST
> > ***
> > > > >>
> > > > >> We're voting upon the source (tag):  rc/1.10.0-rc1
> > > > >> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
> > > > >>
> > > > >> Source Files:
> > > > >> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.
> > > > >> 10.0-incubating-rc1/
> > > > >>
> > > > >> Commit to be voted upon:
> > > > >> https://github.com/apache/incubator-madlib/commit/
> > > > >> ea17530bfe22a1fde173d7fa83508cbcd9924c20
> > > > >>
> > > > >> KEYS file containing PGP Keys we use to sign the release:
> > > > >> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
> > > > >>
> > > > >> To help in tallying the vote, can PMC members please be sure to
> > > > >> indicate "(binding)" with their vote.
> > > > >>
> > > > >> [ ] +1  approve
> > > > >> [ ] +0  no opinion
> > > > >> [ ] -1  disapprove (and reason why)
> > > > >>
> > > > >> --
> > > > >> Satoshi Nagayasu 
> > > > >>
> > > >
> > >
> >
> >
> >
> > --
> > *Ed Espino*
> > *esp...@apache.org *
> >
>



-- 
*Ed Espino*
*esp...@apache.org *

Re: [VOTE] MADlib v1.10-rc1

[Orhan Kislal]

Hi Ed,

Thanks for the review. One of the comments from the previous release was a
preference towards a signature with an Apache id. Since Satoshi-san is not
an Apache committer yet, I took care of the signing process.

Thanks,

Orhan Kislal

On Thu, Feb 16, 2017 at 11:58 AM, Ed Espino  wrote:

> A few MADlib v1.10-rc1 observations from a HAWQ incubator committer.
>
>- The Copyright year (2016) in the NOTICE file needs to be updated to
>2017. I believe this can be handled in next release.
>- As it still applies, similar to a past comment by Roman ([VOTE] MADlib
>v1.9.1-rc2
> c7a78d3a9dc26bf659af94fcfe@%3Cgeneral.incubator.apache.org%3E>)
>- *"* name of the top level folder in the archive is weird. The usual
>practice is to call the top level folder as - ID>*"*
> (example: *apache-madlib-src-1.10-incubating* instead of
>*incubator-madlib*)
>- I'm more curious than anything. Why did Orhan sign the release? I was
>expecting the release manager (Satoshi Nagayasu) to have signed the
> release.
>- Checksums and PGP signature are good.
>-  ASF headers check: I spot checked files added (git whatchanged
>--diff-filter=A) since the last release. ASF headers look good.  Nice
> Job!
>
> I was going to try and build but I ran past my allotted time limit for this
> review. Hopefully, I can try this soon.
>
> Regards,
> -=ed espino
>
> On Thu, Feb 16, 2017 at 10:05 AM, Orhan Kislal  wrote:
>
> > +1
> >
> > Orhan Kislal
> >
> > On Thu, Feb 16, 2017 at 9:23 AM, Joe Hellerstein <
> hellerst...@berkeley.edu
> > >
> > wrote:
> >
> > > +1
> > >
> > > Sent from a telephone.
> > >
> > > > On Feb 16, 2017, at 9:17 AM, Frank McQuillan 
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > Frank McQuillan
> > > >
> > > >> On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu 
> > > wrote:
> > > >>
> > > >> Hello MADlib community,
> > > >>
> > > >> We have created a MADlib 1.10 RC-1, with the artifacts below up for
> a
> > > vote.
> > > >>
> > > >> This will be the 4th release for Apache MADlib (incubating).
> > > >>
> > > >> The main goals of this release are:
> > > >> * new modules (single source shortest path for graph analytics,
> encode
> > > >> categorical variables, K-nearest neighbors)
> > > >> * improvements to existing modules (add grouping support to elastic
> > > >> net and PCA, add cross validation to elastic net, array input for
> > > >> K-means, verbose output option for DT and RF, limit itemset size in
> > > >> association rules, various madpack installer improvements)
> > > >> * platform updates (PostgreSQL 9.6)
> > > >> * bug fixes
> > > >> * doc improvements
> > > >>
> > > >> For more information including release notes, please see:
> > > >> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
> > > >>
> > > >> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST
> ***
> > > >>
> > > >> We're voting upon the source (tag):  rc/1.10.0-rc1
> > > >> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
> > > >>
> > > >> Source Files:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.
> > > >> 10.0-incubating-rc1/
> > > >>
> > > >> Commit to be voted upon:
> > > >> https://github.com/apache/incubator-madlib/commit/
> > > >> ea17530bfe22a1fde173d7fa83508cbcd9924c20
> > > >>
> > > >> KEYS file containing PGP Keys we use to sign the release:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
> > > >>
> > > >> To help in tallying the vote, can PMC members please be sure to
> > > >> indicate "(binding)" with their vote.
> > > >>
> > > >> [ ] +1  approve
> > > >> [ ] +0  no opinion
> > > >> [ ] -1  disapprove (and reason why)
> > > >>
> > > >> --
> > > >> Satoshi Nagayasu 
> > > >>
> > >
> >
>
>
>
> --
> *Ed Espino*
> *esp...@apache.org *
>

Re: [VOTE] MADlib v1.10-rc1

[Frank McQuillan]

+1

Frank McQuillan

On Wed, Feb 15, 2017 at 7:27 PM, Satoshi Nagayasu  wrote:

> Hello MADlib community,
>
> We have created a MADlib 1.10 RC-1, with the artifacts below up for a vote.
>
> This will be the 4th release for Apache MADlib (incubating).
>
> The main goals of this release are:
> * new modules (single source shortest path for graph analytics, encode
> categorical variables, K-nearest neighbors)
> * improvements to existing modules (add grouping support to elastic
> net and PCA, add cross validation to elastic net, array input for
> K-means, verbose output option for DT and RF, limit itemset size in
> association rules, various madpack installer improvements)
> * platform updates (PostgreSQL 9.6)
> * bug fixes
> * doc improvements
>
> For more information including release notes, please see:
> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10
>
> *** Please download, review and vote by Sat Feb 18, 2017 @ 6pm PST ***
>
> We're voting upon the source (tag):  rc/1.10.0-rc1
> https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc1
>
> Source Files:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.
> 10.0-incubating-rc1/
>
> Commit to be voted upon:
> https://github.com/apache/incubator-madlib/commit/
> ea17530bfe22a1fde173d7fa83508cbcd9924c20
>
> KEYS file containing PGP Keys we use to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
>
> To help in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> --
> Satoshi Nagayasu 
>