RE: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

2018-02-16 Thread Meier, Caleb
-1 (binding)

I agree that we should fix the licensing and build issues for this release so 
that we can move onto graduation.

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Adina Crainiceanu [mailto:ad...@usna.edu] 
Sent: Friday, February 16, 2018 11:21 AM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

-1 from me. I think we should fix the licensing, release without any licensing 
issues, and then graduate very soon :)

I'll send an email to close the vote and start another release candidate.

Thank you.

On Fri, Feb 16, 2018 at 11:16 AM, Puja Valiyil  wrote:

> +1 (binding).
> There are two known issues with RC1:
> The licensing issue with Giraph:  This can be fixed in a future 
> release prior to graduation.
> Not being able to build under Windows:  Again, not clear if this is an 
> issue since no one is responding to the other thread about the issue.  
> So I will say Windows support is not a deal breaker here.
>
> On Thu, Feb 15, 2018 at 7:13 PM, Josh Elser  wrote:
>
> > IIRC, the findbugs-annotation artifact is dubious at best in terms 
> > of licensing. I think the "intent" was that it was compatibly 
> > licensed, but the artifacts in Maven totally had it mislabeled.
> >
> > Not something that needs to block your release now, but you should 
> > be taking this up to make sure are I want y'all to graduate soon :)
> >
> >
> > On 2/14/18 11:29 AM, Jeff Dasch wrote:
> >
> >> I just dug through some emails and we did identify this in 3.2.11-RC2.
> We
> >> had a number of other licensing issues on that RC so it is not 
> >> clear to
> me
> >> if this particular finding got dropped, or was determined to be a 
> >> non-issue.  Regardless, this same issue does affect the 3.2.11 release.
> >>
> >> On Wed, Feb 14, 2018 at 10:57 AM, Puja Valiyil 
> wrote:
> >>
> >> I’m confused because that project was in our previous release.  
> >> Didn’t
> we
> >>> upgrade the version of giraph to fix this or am I misremembering?
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Feb 14, 2018, at 10:37 AM, Jeff Dasch  wrote:
> 
>  Again, not sure if this license thing is a blocker.  But if it 
>  is, I
> put
> 
> >>> up
> >>>
>  PR-274 as a fix: 
>  https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_a
>  pache_incubator-2Drya_pull_274=DwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH
>  54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo
>  8=rJpSvZFMvmPo3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek=o6vO6bBa0jDTynG
>  HRmZ8_fDOnNOCrx-srgmEFNVLRjg=
> 
> 
>  On Tue, Feb 13, 2018 at 4:37 PM, Jeff Dasch  wrote:
> >
> > I'm not voting yet, but I did run a license check and got a hit 
> > on
> > this:
> > (GNU Lesser Public License) FindBugs-Annotations
> > (com.google.code.findbugs:annotations:2.0.2 -
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__findbugs.sou
> > rceforge.net_=DwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfx
> > Iq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=rJpSvZFMvmP
> > o3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek=8crfbvCjZv-O9e6T3ASaH2-kAAFnC
> > yKhhS5Bky8dnzA=)
> >
> > which comes from Apache Giraph
> > [INFO] org.apache.rya:rya.giraph:jar:3.2.12-incubating
> > [INFO] +- org.apache.giraph:giraph-core:jar:1.2.0:compile
> > [INFO] |  +- 
> > com.google.code.findbugs:annotations:jar:2.0.2:compile
> >
> > I'm pretty sure we ran into this during the last release.  Are 
> > we
> still
> > good to go on this RC, or do we need to cut a new one that has a
> giraph
> > profile?
> >
> >
> >
> > On Mon, Feb 12, 2018 at 8:51 PM, Adina Crainiceanu 
> > 
> >>
> > wrote:
> >>>
> 
> >> Rya community,
> >>
> >> I am pleased to be calling this vote for the source release of
> Apache
> >>
> > Rya
> >>>
>  (Incubating), version 3.2.12.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apach
> >> e.org_repos_dist_dev_incubator_rya_rya-2D=DwIFaQ=Nwf-pp4xtY
> >> Re0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7Cr
> >> MHCgeo_4WXTD0qo8=rJpSvZFMvmPo3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek&
> >> s=kyxk7CSfvebi0hIqyQQSZExbKVYH-sLAn0yc4O1rzlo=
> >> incubating-3.2.12-rc1/
> >>
> >> Ancillary artifacts such as poms, jars, wars, etc. can be found
> here:
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__repository
> >> .apache.org_content_repositories_=DwIFaQ=Nwf-pp4xtYRe0sCRVM
> >> 8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4
> >> 

RE: Release build fails on Windows

2018-02-16 Thread White, Eric
OK.  These are the test classes that fail for me when building on Windows (in 
rya.shell and rya.streams.integration).  We could potentially add some JUnit 
assumptions to temporarily ignore these classes on Windows until a better 
solution is in place.  That way it would build and we could mark those projects 
as known issues on Windows.

extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/aggregation/AggregationProcessorIT.java
extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/join/JoinProcessorIT.java
extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/projection/MultiProjectionProcessorIT.java
extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/sp/StatementPatternProcessorIT.java
extras/shell/src/test/java/org/apache/rya/shell/AccumuloRyaConnectionCommandsIT.java
extras/shell/src/test/java/org/apache/rya/shell/MongoRyaShellIT.java

-Original Message-
From: White, Eric [mailto:eric.wh...@parsons.com] 
Sent: Friday, February 16, 2018 1:39 PM
To: dev@rya.incubator.apache.org
Subject: RE: Release build fails on Windows

I ignored the 2 test files giving that problem but ran into another build issue 
on 64-bit Windows with Kafka.  It seems there's a problem with Kafka 0.10.0.1 
not correctly bundling RocksDB in the jar (Error message: 
"librocksdbjni-win64.dll was not found inside JAR").  There's a Kafka JIRA 
ticket for this: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_KAFKA-2D4316=DwIGaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ=Suwk7RNCtXna4YgKFMJfmITYVnJzd_AXAck_edQw-zg=HaonPQAcgBYosCJokbdZNJ6bJdBdNkD8huSWgsKFUYo=



This is supposed to be resolved in Kafka 0.10.1 (already released).  I'll see 
if ignoring those failing tests will make the Rya build pass on Windows.



-Original Message-

From: Puja Valiyil [mailto:puja...@gmail.com] 

Sent: Thursday, February 15, 2018 1:42 PM

To: dev@rya.incubator.apache.org

Subject: Re: Release build fails on Windows



Ok, I would vote to mark it as a known issue then.  Is there any concern if the 
release doesn't build under windows?  I don't see that being an issue 
personally.



On Thu, Feb 15, 2018 at 1:32 PM, White, Eric  wrote:



> I can try but that probably won't fix it since it determines that the 

> owner of “user.home” is system and that’s not the same as administrator.

>

> -Original Message-

> From: Puja Valiyil [mailto:puja...@gmail.com]

> Sent: Thursday, February 15, 2018 1:24 PM

> To: dev@rya.incubator.apache.org

> Subject: Re: Release build fails on Windows

>

> Did you try running as an administrator?

> I think that we should probably mark this as a known issue -- I don't 

> feel it should hold up the release.  There have been lots of issues 

> with people building on windows, this is part of a larger issue I feel.

>

> On Thu, Feb 15, 2018 at 1:11 PM, White, Eric 

> wrote:

>

> > I ran into issues building the release (3.2.12-rc1) on a Windows 

> > machine with git bash.  It seems some of the new Rya Shell tests 

> > fail due to the new PathUtils class (from another commit) saying 

> > "Operation of a file in a shared directory is not allowed" when 

> > attempting to add the .rya_shell_history file to "user.home".

> >

> > It seems it expects "user.home" to be owned by the user or an 

> > administrator, but it's owned by the system and fails.

> >

> > Thanks,

> > -Eric White

> >

>



RE: Release build fails on Windows

2018-02-16 Thread White, Eric
I ignored the 2 test files giving that problem but ran into another build issue 
on 64-bit Windows with Kafka.  It seems there's a problem with Kafka 0.10.0.1 
not correctly bundling RocksDB in the jar (Error message: 
"librocksdbjni-win64.dll was not found inside JAR").  There's a Kafka JIRA 
ticket for this: https://issues.apache.org/jira/browse/KAFKA-4316

This is supposed to be resolved in Kafka 0.10.1 (already released).  I'll see 
if ignoring those failing tests will make the Rya build pass on Windows.

-Original Message-
From: Puja Valiyil [mailto:puja...@gmail.com] 
Sent: Thursday, February 15, 2018 1:42 PM
To: dev@rya.incubator.apache.org
Subject: Re: Release build fails on Windows

Ok, I would vote to mark it as a known issue then.  Is there any concern if the 
release doesn't build under windows?  I don't see that being an issue 
personally.

On Thu, Feb 15, 2018 at 1:32 PM, White, Eric  wrote:

> I can try but that probably won't fix it since it determines that the 
> owner of “user.home” is system and that’s not the same as administrator.
>
> -Original Message-
> From: Puja Valiyil [mailto:puja...@gmail.com]
> Sent: Thursday, February 15, 2018 1:24 PM
> To: dev@rya.incubator.apache.org
> Subject: Re: Release build fails on Windows
>
> Did you try running as an administrator?
> I think that we should probably mark this as a known issue -- I don't 
> feel it should hold up the release.  There have been lots of issues 
> with people building on windows, this is part of a larger issue I feel.
>
> On Thu, Feb 15, 2018 at 1:11 PM, White, Eric 
> wrote:
>
> > I ran into issues building the release (3.2.12-rc1) on a Windows 
> > machine with git bash.  It seems some of the new Rya Shell tests 
> > fail due to the new PathUtils class (from another commit) saying 
> > "Operation of a file in a shared directory is not allowed" when 
> > attempting to add the .rya_shell_history file to "user.home".
> >
> > It seems it expects "user.home" to be owned by the user or an 
> > administrator, but it's owned by the system and fails.
> >
> > Thanks,
> > -Eric White
> >
>


Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

2018-02-16 Thread Puja Valiyil
+1 (binding).
There are two known issues with RC1:
The licensing issue with Giraph:  This can be fixed in a future release
prior to graduation.
Not being able to build under Windows:  Again, not clear if this is an
issue since no one is responding to the other thread about the issue.  So I
will say Windows support is not a deal breaker here.

On Thu, Feb 15, 2018 at 7:13 PM, Josh Elser  wrote:

> IIRC, the findbugs-annotation artifact is dubious at best in terms of
> licensing. I think the "intent" was that it was compatibly licensed, but
> the artifacts in Maven totally had it mislabeled.
>
> Not something that needs to block your release now, but you should be
> taking this up to make sure are I want y'all to graduate soon :)
>
>
> On 2/14/18 11:29 AM, Jeff Dasch wrote:
>
>> I just dug through some emails and we did identify this in 3.2.11-RC2.  We
>> had a number of other licensing issues on that RC so it is not clear to me
>> if this particular finding got dropped, or was determined to be a
>> non-issue.  Regardless, this same issue does affect the 3.2.11 release.
>>
>> On Wed, Feb 14, 2018 at 10:57 AM, Puja Valiyil  wrote:
>>
>> I’m confused because that project was in our previous release.  Didn’t we
>>> upgrade the version of giraph to fix this or am I misremembering?
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 14, 2018, at 10:37 AM, Jeff Dasch  wrote:

 Again, not sure if this license thing is a blocker.  But if it is, I put

>>> up
>>>
 PR-274 as a fix: https://github.com/apache/incubator-rya/pull/274


 On Tue, Feb 13, 2018 at 4:37 PM, Jeff Dasch  wrote:
>
> I'm not voting yet, but I did run a license check and got a hit on
> this:
> (GNU Lesser Public License) FindBugs-Annotations
> (com.google.code.findbugs:annotations:2.0.2 -
> http://findbugs.sourceforge.net/)
>
> which comes from Apache Giraph
> [INFO] org.apache.rya:rya.giraph:jar:3.2.12-incubating
> [INFO] +- org.apache.giraph:giraph-core:jar:1.2.0:compile
> [INFO] |  +- com.google.code.findbugs:annotations:jar:2.0.2:compile
>
> I'm pretty sure we ran into this during the last release.  Are we still
> good to go on this RC, or do we need to cut a new one that has a giraph
> profile?
>
>
>
> On Mon, Feb 12, 2018 at 8:51 PM, Adina Crainiceanu 
>>
> wrote:
>>>

>> Rya community,
>>
>> I am pleased to be calling this vote for the source release of Apache
>>
> Rya
>>>
 (Incubating), version 3.2.12.
>>
>> The source zip, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
>> incubating-3.2.12-rc1/
>>
>> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
>> https://repository.apache.org/content/repositories/
>> orgapacherya-1009/org/apache/rya/
>>
>> The Git tag is rya-incubating-3.2.12-rc1
>> The Git commit ID is e9ecf7fae76e308cfc0d90684ce684493482266c
>> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
>> a=commit;h=e9ecf7fae76e308cfc0d90684ce684493482266c
>>
>>
>> Checksums of rya-project-3.2.12-source-release.zip:
>> SHA512:8059adff3a264cdcc85edb8ab1c820d87d4e2adbdfd4eebfcd7d2
>> 7b9a3c8c2af8cd09cb39b91ccb5170fe37159b1360078ef8e61321e7f6ca
>> e6141442bbf8dda
>> SHA1: 64296d86923dae11294dcff0719cfcb9522a744d
>> MD5: 9c55ae7f811afaa147ebb7f652543620
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/adina.asc
>>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>>
>> Issues that were closed/resolved for this release are here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12319020=12341570
>>
>>
>> The vote will be open for at least 72 hours until end of Thursday,
>> February
>> 15, 2018 ET.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.
>>
> Then
>>>
 please vote:
>>
>> [ ] +1 Release this package as rya-project-3.2.12
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>>
>>
>> Thank you,
>> Adina
>>
>> --
>> Dr. Adina Crainiceanu
>> Associate Professor
>> Computer Science Department
>> United States Naval Academy
>> 410-293-6822 <(410)%20293-6822>
>> ad...@usna.edu
>> http://www.usna.edu/Users/cs/adina/
>>
>>
>
>
>>>
>>


Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

2018-02-16 Thread Brown, Jennifer
-1 (binding)

Recommend addressing the licensing issue w/ PR-274
https://github.com/apache/incubator-rya/pull/274

Best Regards,

Jen

Jennifer Brown
Project Manager, Semantic Technologies
PARSONS
1911 N. Fort Myer Dr. Ste 800
Arlington, VA 22209
Phone: (703) 797-3136
Fax: (703) 522-6310
jennifer.br...@parsons.com
www.parsons.com

On Feb 12, 2018, at 8:51 PM, Adina Crainiceanu 
> wrote:

Rya community,

I am pleased to be calling this vote for the source release of Apache Rya
(Incubating), version 3.2.12.

The source zip, including signatures, digests, etc. can be found at:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_rya_rya-2D=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=HMTvfTdBWNxQdME9N0vSTtA4mmAVI5pHOIUCbLJsto8=
incubating-3.2.12-rc1/

Ancillary artifacts such as poms, jars, wars, etc. can be found here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=brqJeyfEhqBwGxW5snf0-0tVjuU3heqv04r2yPzgLN0=
orgapacherya-1009/org/apache/rya/

The Git tag is rya-incubating-3.2.12-rc1
The Git commit ID is e9ecf7fae76e308cfc0d90684ce684493482266c
https://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dwip-2Dus.apache.org_repos_asf-3Fp-3Dincubator-2Drya.git-3Ba-3Dcommit-3Bh-3De9ecf7fae76e308cfc0d90684ce684493482266c=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=2DGpjxWzZDe5QGERXx6JRwEFE2pkMSBrIuNvLEne8yk=


Checksums of rya-project-3.2.12-source-release.zip:
SHA512:8059adff3a264cdcc85edb8ab1c820d87d4e2adbdfd4eebfcd7d2
7b9a3c8c2af8cd09cb39b91ccb5170fe37159b1360078ef8e61321e7f6cae6141442bbf8dda
SHA1: 64296d86923dae11294dcff0719cfcb9522a744d
MD5: 9c55ae7f811afaa147ebb7f652543620

Release artifacts are signed with the following key:
https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.org_keys_committer_adina.asc=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=SLPPTU0mWQTzBDacmySCu70WztRiB5l1lRu9nEapzwA=

KEYS file available here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_release_incubator_rya_KEYS=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=HGH7_h_YOvum5YH4o0tWt53MMLk59twtO21mMMhBymk=

Issues that were closed/resolved for this release are here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_secure_ReleaseNote.jspa-3F=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=DRv_e4wsgzLkYMa2YAlT0VY7cCZt-_2KH9jC0YrCzug=
projectId=12319020=12341570


The vote will be open for at least 72 hours until end of Thursday, February
15, 2018 ET.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.  Then
please vote:

[ ] +1 Release this package as rya-project-3.2.12
[ ] +0 no opinion
[ ] -1 Do not release this package because because...


Thank you,
Adina

--
Dr. Adina Crainiceanu
Associate Professor
Computer Science Department
United States Naval Academy
410-293-6822 <(410)%20293-6822>
ad...@usna.edu
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usna.edu_Users_cs_adina_=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=DiVRntLDtTFjcbOSmTIDdpIthE7hm-H-kG0ng0wNw4M=yiWkVM0MVH15dUyy3Ri60-0U8_CVfG60CU2r5as2W24=