Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

Nope, that should be fine. On Fri, Aug 26, 2016 at 12:45 AM, Walter Ray-Dulany wrote: > Does it matter that this release candidate is at > https://org/apache/pirk/pirk/ > instead of ...org/apache/pirk/apache-pirk/ like the last candidate > was? > > Walter > > On

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

Does it matter that this release candidate is at https://org/apache/pirk/pirk/ instead of ...org/apache/pirk/apache-pirk/ like the last candidate was? Walter On Thu, Aug 25, 2016 at 2:53 PM, Tim Ellison wrote: > On 25/08/16 17:23, Ellison Anne Williams wrote:

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

+1 (binding) - Verified SHA1, MD5, and signature for artifact - Checked L files - all reflect source-only - Successfully built the code and ran the tests - RAT checks pass - Export information contained in README On Thu, Aug 25, 2016 at 12:25 PM, Suneel Marthi wrote: > I

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

+1 binding 1. Verified the ReadMe for Export controls 2. Verified Hashs and Sigs 3. RAT check passes 4. Clean build from Source and all tests pass On Thu, Aug 25, 2016 at 12:23 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > This is the vote for release 0.1.0 of Apache

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

I think we shuld close the vote once we hit a quorum of 3 +1 (binding) votes. On Thu, Aug 25, 2016 at 12:23 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > This is the vote for release 0.1.0 of Apache Pirk (incubating); it is a > source-only release (no binary artifacts).

[VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

Hi, This is the vote for release 0.1.0 of Apache Pirk (incubating); it is a source-only release (no binary artifacts). We have to re-vote after correcting the crypto export issues that IMPC members found. As this vote reflects our crypto export corrections to our last candidate, it will run

Re: [GitHub] incubator-pirk issue #79: Removed the and

Just went through the release steps and the artifacts did not automatically deploy to the dist directory - I just added them manually a second ago... On Thu, Aug 25, 2016 at 11:33 AM, ellisonanne wrote: > Github user ellisonanne commented on the issue: > >

[GitHub] incubator-pirk pull request #79: Removed the and

Github user asfgit closed the pull request at: https://github.com/apache/incubator-pirk/pull/79 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: [GitHub] incubator-pirk issue #79: Removed the and

Ok - got it. I will merge and then re-do the release with these settings. On Thu, Aug 25, 2016 at 11:30 AM, Suneel Marthi wrote: > We are not changing the Nexus staging at all - the new URL would be the > Nexus staging repo. > > This was the first comment that Justin

[GitHub] incubator-pirk pull request #74: PIRK-4 [WIP] Add Streaming Implementation f...

Github user smarthi commented on a diff in the pull request: https://github.com/apache/incubator-pirk/pull/74#discussion_r7627 --- Diff: pom.xml --- @@ -112,12 +112,14 @@ benchmarks 1.8 1.7.21 - 2.6.2 +

[GitHub] incubator-pirk issue #79: Removed the and

Github user ellisonanne commented on the issue: https://github.com/apache/incubator-pirk/pull/79 Why are we making this change? It seems to be reasonable to keep the deploy location as our Nexus staging repo and then to move the artifacts over to the dist repo once everything passes,

[GitHub] incubator-pirk pull request #80: Add required export notice to README.md

Github user asfgit closed the pull request at: https://github.com/apache/incubator-pirk/pull/80 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[CANCEL] [VOTE] Apache Pirk 0.1.0-incubating Release

The Apache Pirk 0.1.0-incubating release vote is cancelled. We have fixed our cryptographic export items as described below, but must regenerate the artifacts due to the required additions to the README. We will regenerate, vote within the PPMC, and then submit the vote again to the IPMC.

Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

Hi Guys, Thanks so much for jumping on this - you beat me to it this morning! I will cancel the IMPC vote, re-spin and push the artifacts, and start over again. Ellison Anne On Thu, Aug 25, 2016 at 7:52 AM, Suneel Marthi wrote: > On Thu, Aug 25, 2016 at 7:51 AM, Suneel

Re: Distributed Tests Before Accepting PR

On 23/08/16 14:51, Ellison Anne Williams wrote: > The distributed tests are self contained except for letting the application > know (1) where to find Elasticsearch and (2) setting spark.home for the > SparkLauncher. For MapReduce distributed testing that reads from hdfs, it > should work

Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

On Thu, Aug 25, 2016 at 7:51 AM, Suneel Marthi wrote: > Thanks Tim. > > Next Steps to move forward with the Release (for the Release Manager): > > 1. Merge PR#80 and PR#79 to codebase. > > 2. Respond to general@ that we'll be pushing new artifacts with updated > ReadMe. > >

Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

Thanks Tim. Next Steps to move forward with the Release (for the Release Manager): 1. Merge PR#80 and PR#79 to codebase. 2. Respond to general@ that we'll be pushing new artifacts with updated ReadMe. 3. Drop the existing Staging artifacts from Nexus 4. Rollback the present Release. 5.

[GitHub] incubator-pirk pull request #80: Add required export notice to README.md

Github user smarthi commented on a diff in the pull request: https://github.com/apache/incubator-pirk/pull/80#discussion_r76227425 --- Diff: README.md --- @@ -86,6 +86,32 @@ Pirk employs generic [data and query schemas](http://pirk.incubator.apache.org/f See the

Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

On 25/08/16 01:26, Ellison Anne Williams wrote: > Yes, as per http://www.apache.org/dev/crypto.html -- > > The code falls under ECCN 5D002, so we are good there. > > We need to: > > (1) Notify the USG via the sending the specified email Done. I cc:'d the dev list, but it may be stuck in

[GitHub] incubator-pirk pull request #80: Add required export notice to README.md

Github user tellison commented on a diff in the pull request: https://github.com/apache/incubator-pirk/pull/80#discussion_r76224576 --- Diff: README.md --- @@ -86,6 +86,32 @@ Pirk employs generic [data and query schemas](http://pirk.incubator.apache.org/f See the

TSU NOTIFICATION - Encryption

SUBMISSION TYPE: TSU SUBMITTED BY: Tim Ellison SUBMITTED FOR:The Apache Software Foundation POINT OF CONTACT: Secretary, The Apache Software Foundation FAX: +1-919-573-9199 MANUFACTURER(S): The Apache Software Foundation PRODUCT NAME/MODEL #:

Update ASF ECCN classification page (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

I'm on it. Regards, Tim On 25/08/16 03:33, Suneel Marthi wrote: > On Wed, Aug 24, 2016 at 9:09 PM, Suneel Marthi > wrote: > >> >> >> On Wed, Aug 24, 2016 at 8:26 PM, Ellison Anne Williams < >> eawilliamsp...@gmail.com> wrote: >> >>> Yes, as per