Re: [VOTE] Accept StreamPark into the Apache Incubator

[Thomas Weise]

+1 (binding)

Thanks,
Thomas


On Wed, Aug 24, 2022 at 3:08 AM Kelu Tao  wrote:

> +1 (non-binding)
>
> Good Luck!
>
> On 2022/08/24 03:55:26 tison wrote:
> > Hi all,
> >
> > Following up on the [DISCUSS] thread on StreamPark[1], I would like to
> call
> > a VOTE to accept StreamPark into the Apache Incubator, please check out
> the
> > StreamPark Proposal from the incubator wiki[2].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring StreamPark into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring StreamPark into the Incubator, because...
> >
> > The vote will open at least for 72 hours, and only votes from the
> Incubator
> > PMC are binding, but votes from everyone are welcome.
> >
> > Best,
> > tison.
> >
> > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3
> > [2]
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Hudi (Incubating) as a TLP

[Thomas Weise]

+1 (binding)


On Fri, May 15, 2020 at 6:50 PM Vinoth Chandar  wrote:

> Hello all,
>
> I would like to call for a VOTE for graduating Apache Hudi (Incubating), as
> a top level project.
>
> Please vote on the resolution pasted below to graduate Apache Hudi from the
> incubator to a Top Level Project.
>
> [ ] +1 Graduate Apache Hudi from the Incubator.
> [ ] +0
> [ ] -1 Don't graduate Apache Hudi from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> Apache Hudi (Incubating) entered the incubator in Jan 2019, the community
> has grown vibrantly since, with all the design, development happening on
> the Apache infrastructure, the "Apache way".
>
> To list a few of the community's achievements,
>
> - Accepted > 500 patches from 90 contributors, including 15+ new  design
> proposals
> - Performed 3 releases with 3 different release managers [5]
> - Invited 5 new committers (all of them accepted)
> - invited 3 of those new committers to join the PMC (all of them accepted)
> - Migrated our web site to ASF infrastructure [1]
> - Migrated developer conversations to the list at d...@hudi.apache.org
> - Migrated all issue tracking to JIRA [2]
> - Apache Hudi name search has been approved [3]
> - Assessed ourselves against the Apache Project maturity matrix [4]
> - We have built a meritocratic, open collaborative process, the Apache way
> - Our proposed PMC is diverse and consists of members from ~10
> organizations
>
> We discussed our readiness for graduation as a community [6] and voted
> unanimously in favor [7] (results summarized in [8]).  We have collaborated
> on a resolution for graduation, including PMC membership and PMC chair. We
> have also addressed the issues raised on the general@incubator DISCUSS
> thread [9].
>
>
> [1] https://hudi.apache.org
>
> [2] https://issues.apache.org/jira/projects/HUDI/
>
> [3] https://jira.apache.org/jira/browse/PODLINGNAMESEARCH-162
>
> [4]
>
> https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
>
>
> [5] https://hudi.apache.org/releases.html
> [6]
>
> https://lists.apache.org/thread.html/rc98303d9f09665af90ab517ea0baeb7c374e9a5478d8424311e285cd%40%3Cdev.hudi.apache.org%3E
> [7]
>
> https://lists.apache.org/thread.html/rc19cedf6bb423cfc24efea27d8952a2224370a7679bab74d05de19b2%40%3Cdev.hudi.apache.org%3E
> [8]
>
> https://lists.apache.org/thread.html/r7b5c169c1bc3a1acaa35f43ff5388f5fc8b60746d423043464fcf5df%40%3Cdev.hudi.apache.org%3E
> [9]
>
> https://lists.apache.org/thread.html/r10d8c2038f1131c4da3e0cc2759da3554fab846bd623830251327b27%40%3Cgeneral.incubator.apache.org%3E
>
> Establish the Apache Hudi Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of the
> Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to providing atomic upserts and incremental data streams on Big Data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Hudi Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hudi Project be and hereby is responsible for the
> creation and maintenance of software related to providing atomic upserts
> and incremental data streams on Big Data; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hudi" be and hereby is
> created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache Hudi Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Hudi Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed
> to serve as the initial members of the Apache Hudi Project:
>
>  * Anbu Cheeralan   
>
>  * Balaji Varadarajan    
>
>  * Bhavani Sudha Saktheeswaran   
>
>  * Luciano Resende 
>
>  * Nishith Agarwal
>
>  * Prasanna Rajaperumal
>
>  * Shaofeng Li   
>
>  * Steve Blackmon  
>
>  * Suneel Marthi  
>
>  * Thomas Weise
>
>  * Vino Yang   
>
>  * Vinoth Chandar
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Vinoth Chandar be appointed to
> the office of Vice President, Apache H

Re: [DISCUSS] Graduate Apache Hudi (Incubating) as a TLP

[Thomas Weise]

+1

Excellent community-building work. I'm impressed by the inclusiveness and
diversity of the community and the enthusiasm of many of the individuals.
This puts Hudi on a solid footing, it also isn't dominated by a single
commercial entity.

The PPMC has been attentive to growing the committer and PPMC pipeline and
also quite transparent in that regard. Candidates are evaluated
periodically and contributions acknowledged and appreciated.


On Mon, May 11, 2020 at 11:58 AM Vinoth Chandar  wrote:

> Hello everyone,
>
> Apache Hudi (Incubating) entered the incubator in Jan 2019, the community
> has grown vibrantly since, with all the design, development happening on
> the Apache infrastructure, the "Apache way".
>
> To list a few of the community's achievements,
>
> - Accepted > 500 patches from 90 contributors, including 15+ new  design
> proposals
> - Performed 3 releases with 3 different release managers [5]
> - Invited 5 new committers (all of them accepted)
> - invited 3 of those new committers to join the PMC (all of them accepted)
> - Migrated our web site to ASF infrastructure [1]
> - Migrated developer conversations to the list at d...@hudi.apache.org
> - Migrated all issue tracking to JIRA [2]
> - Apache Hudi name search has been approved [3]
> - Assessed ourselves against the Apache Project maturity matrix [4]
> - We have built a meritocratic, open collaborative process, the Apache way
> - Our proposed PMC is diverse and consists of members from ~10
> organizations
>
> We discussed our readiness for graduation as a community [6] and voted
> unanimously in favor [7] (results summarized in [8]).
> We have collaborated on a resolution for graduation, including PMC
> membership and PMC chair. Please refer to the draft resolution below and
> provide any comments, feedback.
> The discussion will remain open for at least 72 hours.
>
>
> [1] https://hudi.apache.org
>
> [2] https://issues.apache.org/jira/projects/HUDI/
>
> [3] https://jira.apache.org/jira/browse/PODLINGNAMESEARCH-162
>
> [4]
>
> https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
>
>
> [5] https://hudi.apache.org/releases.html
> [6]
>
> https://lists.apache.org/thread.html/rc98303d9f09665af90ab517ea0baeb7c374e9a5478d8424311e285cd%40%3Cdev.hudi.apache.org%3E
> [7]
>
> https://lists.apache.org/thread.html/rc19cedf6bb423cfc24efea27d8952a2224370a7679bab74d05de19b2%40%3Cdev.hudi.apache.org%3E
> [8]
>
> https://lists.apache.org/thread.html/r7b5c169c1bc3a1acaa35f43ff5388f5fc8b60746d423043464fcf5df%40%3Cdev.hudi.apache.org%3E
>
> Establish the Apache Hudi Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of the
> Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to providing atomic upserts and incremental data streams on Big Data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Hudi Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hudi Project be and hereby is responsible for the
> creation and maintenance of software related to providing atomic upserts
> and incremental data streams on Big Data; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hudi" be and hereby is
> created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache Hudi Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Hudi Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed
> to serve as the initial members of the Apache Hudi Project:
>
>  * Anbu Cheeralan   
>
>  * Balaji Varadarajan
>
>  * Bhavani Sudha Saktheeswaran   
>
>  * Luciano Resende 
>
>  * Nishith Agarwal
>
>  * Prasanna Rajaperumal
>
>  * Shaofeng Li   
>
>  * Steve Blackmon  
>
>  * Suneel Marthi  
>
>  * Thomas Weise
>
>  * Vino Yang   
>
>  * Vinoth Chandar
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Vinoth Chandar be appointed to
> the office of Vice President, Apache Hudi, to serve in accordance with and
> subject to the direction of the Board of Directors and

Re: [DISCUSS] Graduate Apache Hudi (Incubating) as a TLP

[Thomas Weise]

On Mon, May 11, 2020 at 8:58 PM Justin Mclean 
wrote:

> Hi,
>
> > Why having inactive PMC members is not a big deal now?  What's the point
> of
> > keeping them if they r inactive and do nothing or have no interest in the
> > project?
>
> At some point in the future that may become active again or they may plan
> to be more active in the near future. Having a few extra people on the PMC
> doesn’t hurt a project if they are inactive.
>
> > There is an inactive IPMC member on the proposed PMC - who didn't
> > have time, or bandwidth to help in any way on the project but yet chose
> to
> > be part of and expressed his intent to be on the proposed PMC.
>
> I would suggest the project discusses it with them.
>
> BTW I also agree Mentors shouldn't automatically become part of the new
> PMC if they did not help.
>

That question was actually asked and there are only mentors on the proposed
PMC that explicitly expressed they are interested to stay on.

The case Suneel raises is one where no merit was earned, which may be worth
discussing on private@ indeed.

Thanks,
Thomas

Re: [VOTE] Apache Hudi (incubating) 0.5.2 RC2

[Thomas Weise]

+1 (binding)

* mvn clean package from downloaded source successfully
* checked signature and hash
* checked LICENSE/NOTICE - there is a minor issue which should be corrected
in the next release

According to [1], LICENSE should mention the version of included
dependencies, since their license can also change.

"NOTE: It's also possible to include the text of the 3rd party license
within the LICENSE file. This is best reserved for short licenses. It's
important to specify the version of the dependency as licenses are
sometimes changed."

The NOTICE file now has the bundled dependencies bubbled up. I'm not sure
if there was a need to add all of these (though there is no harm). There
appears to be conflicting information in [1].

"Under normal circumstances, there is no need to modify NOTICE."

"If the dependency supplies a NOTICE file, its contents must be analyzed
and the relevant portions bubbled up into the top-level NOTICE file."

Thanks,
Thomas

[1] http://www.apache.org/dev/licensing-howto.html#alv2-dep



On Sun, Mar 22, 2020 at 12:22 AM vino yang  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
> FileSystem compatible storage) and provide ability to query them.
>
> The Apache Hudi (incubating) community has voted on the release candidate
> and approved. The new source release candidate version is
> 0.5.2-incubating-rc2
>
> Results: 6 binding +1 votes
>
> Here is the voting
> thread:
> https://lists.apache.org/thread.html/r7d8b4831666446bdf19fb6365090ad8c5975b5221e66184ccb24b7e2%40%3Cdev.hudi.apache.org%3E
>
> Here is the voting result
> email:
> https://lists.apache.org/thread.html/rf4a43dbb6171b9e1db236246afbc49979e4dcca87b8a09f3de19a2b8%40%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the release of Apache Hudi
> (incubating). Please review and vote on the release candidate #2 for the
> version 0.5.2, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-0.5.2-incubating-rc2" [5],
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346606
>
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc2/
>
> [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>
> [4] https://repository.apache.org/content/repositories/orgapachehudi-1019
>
> [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc2
>
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=2
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> Best,
>
> vino
>

Re: [VOTE] Apache Hudi (incubating) 0.5.2 RC1

[Thomas Weise]

+1 (binding)

* mvn clean package from downloaded source successfully
* checked signature and hash


On Sun, Mar 15, 2020 at 7:58 PM vino yang  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
> FileSystem compatible storage) and provide ability to query them.
>
> The Apache Hudi (incubating) community has voted on the release candidate
> and approved. The new source release candidate version is
> 0.5.2-incubating-rc1
>
> Results: 6 binding +1 votes
>
> Here is the voting
> thread:
> https://lists.apache.org/thread.html/rf687b44fb8d5e9073c2918a0c366352379ddf01632832adcbfcc060e%40%3Cdev.hudi.apache.org%3E
>
> Here is the voting result
> email:
> https://lists.apache.org/thread.html/rfaad30944d931d07c7a3f8b143b810891d9d80ad61fc6a1f5b7c0dcf%40%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the release of Apache Hudi
> (incubating). Please review and vote on the release candidate #1 for the
> version 0.5.2, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-0.5.2-incubating-rc1" [5],
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346606
>
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc1/
>
> [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>
> [4] https://repository.apache.org/content/repositories/orgapachehudi-1018/
>
> [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc1
>
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=1
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> Best,
>
> vino
>

Re: [VOTE} Apache Hudi (incubating) 0.5.0 RC6

[Thomas Weise]

+1 (binding)

(forward from dev@)

On Sat, Oct 19, 2019 at 3:04 PM  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD
> Incrementals. Apache Hudi (incubating) manages storage of large analytical
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible
> storage) and provide ability to query them.
>
> The previous source release candidate 0.5.0-incubating-rc5 had licensing
> concerns (Please see
> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
> .
>
> We have addressed them in the new source release candidate (RC#6). The
> Apache Hudi (incubating) community has voted on this new release candidate
> and approved. The new source release candidate version is
> 0.5.0-incubating-rc6
>
> Results: 4 binding +1 votes
>
> Here is the voting thread:
> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> Here is the voting result email:
> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the first release of Apache
> Hudi (incubating). Please review and vote on the release candidate #5 for
> the version 0.5.0, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
>
>   - JIRA release notes [1]
>   - The official Apache source release and binary convenience releases to
> be deployed to dist.apache.org [2], which are signed with the key with
> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
>   - all artifacts to be deployed to the Maven Central Repository [4]
>   - source code tag "release-0.5.0-incubating-rc6" [5]
>
>   [1]
> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346087
>   [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
>   [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>   [4]
> https://repository.apache.org/content/repositories/orgapachehudi-1006/
>   [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast
>
> Thanks,
> Balaji.V
> (on behalf of Apache Hudi PPMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release DataSketches-hive 1.0.0-incubating-RC1

[Thomas Weise]

Just a question from my side:

Should NOTICE include "(incubating)" or is this no longer a requirement?

https://github.com/apache/incubator-datasketches-hive/blob/1.1.X-incubating/NOTICE

Thanks,
Thomas


On Tue, Oct 8, 2019 at 10:17 AM Dave Fisher  wrote:

> Carrying over my +1 (binding)
>
> Regards,
> Dave
>
> > On Oct 7, 2019, at 2:15 PM, leerho  wrote:
> >
> > ### NEW COMPONENT! ###
> >
> > Hello IPMC and Apache DataSketches Community,
> >
> > 1. This is a call for vote to release Apache DataSketches-hive version:
> > 1.0.0-incubating-RC1
> >
> >NOTE 1: This is the Hive adaptors component of the DataSketches
> library
> > that enables Apache Hive to access the datasketches-java core library.
> >
> >  A. Results from the PPMC vote:
> >
> > - 3 (+1 binding) votes.
> >
> > - The vote thread can be found at the Permalink:
> >
> >
> https://mail-archives.apache.org/mod_mbox/datasketches-dev/201910.mbox/%3cca+uapntlptpic78pyo6fs9mokafo-yhxo9s9yz3-qrkzjcc...@mail.gmail.com%3e
> >
> >  B. Testing/actions/votes performed by the voters in the PPMC Stage 1:
> >
> >- Furkan Kamaci (+1 binding)
> > - Incubating in name
> > - DISCLAIMER exists
> > - LICENSE and NOTICE are fine
> > - No unexpected binary files
> > - Checked PGP signatures
> > - Checked Checksums
> > - Code compiles and tests successfully run
> >
> > I have one objection:
> > - src/main/javadoc/stylesheet.css file has missing Apache
> > license header. (This file has been removed in master)
> >
> >- Dave Fisher (+1 binding)
> >- I checked the same as Furkan.
> >
> >I am concerned that you were downloading from
> repository.apache.org
> > for many of the artifacts.
> >This repos is used by apache projects to stage for release and
> some
> > organizations do get their
> >IP addresses banned for over use of it. (we are still discussing
> > with Dave to understand the issue here)
> >
> >- Liang Chen (+1 binding)
> >- Incubating in name
> >- DISCLAIMER exists
> >- LICENSE and NOTICE are fine
> >- No unexpected binary files
> >- Checked checksums
> >
> > 2. Source repository:
> >- https://github.com/apache/incubator-datasketches-hive
> >
> >Git Tag for this release:
> >-
> >
> https://github.com/apache/incubator-datasketches-hive/tree/1.0.0-incubating-RC1
> > on branch 1.0.X-incubating
> >
> >Git HashId for this release starts with: 5319e72
> >
> > 3. The Release Candidate / Zip Repository:
> >-
> >
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/hive/1.0.0-incubating-RC1/
> >
> >The public signing key can be found in the KEYS file:
> >- https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS
> >
> >The artifacts have been signed with --keyid-format SHORT : 8CD4A902
> >
> > 4. Repository: [Nexus](http://repository.apache.org) (Jar Artifacts):
> >-
> >
> https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-hive/1.0.0-incubating/
> >
> > 5. Build & Test Guide:
> >-
> >
> https://github.com/apache/incubator-datasketches-hive/blob/1.0.0-incubating-RC1/README.md
> >
> > 6. This vote is the 2nd stage vote:
> >   - This voting process will remain open for at least 72 hours
> > and until at least 3 (+1) IPMC votes or a majority of (+1) are
> > acquired.
> >
> > Please vote accordingly:
> >
> >[ ] +1 approve
> >[ ] +0 no opinion
> >[ ] -1 disapprove with the reason
> >
> > Thanks,
> > Lee Rhodes
> > lee...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept DataSketches into the Apache Incubator

[Thomas Weise]

+1 (binding)


On Sat, Mar 16, 2019, 3:53 AM 吴晟 Sheng Wu  wrote:

> +1 binding
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "Paul King";
> Date:  Sat, Mar 16, 2019 06:47 PM
> To:  "general";
>
> Subject:  Re: [VOTE] Accept DataSketches into the Apache Incubator
>
>
>
> +1 (binding)
>
>
> On Sat, Mar 16, 2019 at 4:30 PM Liang Chen 
> wrote:
>
> > Hi
> >
> > +1(binding)
> >
> > Regards
> > Liang
> >
> >
> > Kenneth Knowles wrote
> > > Hi all,
> > >
> > > We've discussed the proposal for the DataSketches project in [1] and
> [2].
> > > The
> > > proposal itself has been put on the wiki [3].
> > >
> > > Per incubator rules [4] I'd like to call a vote to accept the new
> > > "DataSketches" project as a podling in the Apache Incubator.
> > >
> > > A vote for accepting a new Apache Incubator podling is a majority vote.
> > > Everyone is welcome to vote, only Incubator PMC member votes are
> binding.
> > > It would be helpful (but not required) if you could add a comment
> stating
> > > whether your vote is binding or non-binding.
> > >
> > > This vote will run for at least 72 hours (but I expect to keep it open
> > for
> > > longer). Please VOTE as follows:
> > >
> > > [ ] +1 Accept DataSketches into the Apache Incubator
> > > [ ] +0 Abstain
> > > [ ] -1 Do not accept DataSketches into the Apache Incubator because ...
> > >
> > > Thanks to everyone who contributed to the proposal and discussions.
> > >
> > > Kenn
> > >
> > > [1]
> > >
> >
> https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E
> > > [2]
> > >
> >
> https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E
> > > [3] https://wiki.apache.org/incubator/DataSketchesProposal
> > > [4] https://incubator.apache.org/guides/proposal.html#the_vote
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-incubator-general.996316.n3.nabble.com/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check (was: .... introduce "[DISCUSS]" threads for podling ... release candidates))

[Thomas Weise]

Currently mentors need to be IPMC members. Is that really necessary?
Alternatively mentors could be given all required powers through the PPMC
membership and the IPMC could be more focused on long term direction and
improving the incubator as a whole. IPMC already votes on incubator
proposals and nominated mentors. IPMC could take more of an observer role
and only intervene when there is clearly something wrong with a podling
(similar how the board would with a TLP). Podling reports and graduation
proposal provide the opportunity to catch everything that mentors might
have missed.

Mentors that are active over a long time and show interest in the overall
direction of the incubator, could become IPMC candidates. That would be
similar to how TLPs consider PMC membership.

Thomas

On Sun, Mar 3, 2019 at 12:13 AM Alex Harui  wrote:

> As a peanut, IMO, it could be that the root problem is that the drive-by
> folks are discussing topics that are too subjective at a critical time (to
> get a release out), not the number of folks who can drive-by.  I'm not even
> in the IPMC, and I can still follow general@ and offer opinions.
>
> Podlings would have their lives improved if there were more folks
> available to help in little increments if the help was consistent.  It
> would be a stronger community if more people could help pound a nail or fix
> a flat tire.  It would take the load off the folks in charge.  More people
> would get more done with less burnout.
>
> In some ways, Roy's suggestion to stop having an IPMC vote as a gate for a
> podling release can help by making it less critical to get someone official
> to rule on something "now".  Just ship it, note it in the bug tracker, and
> get to it when you can find someone to help you or take your time resolving
> it, gathering different opinions and coming up with a solution, even a
> temporary one.  Not all issues need to be addressed before graduation,
> IMO.  Some issues just aren't stop-ship and won't ruin the legal shield or
> put the ASF in legal jeopardy.  Policy issues are not always legal issues.
> In fact, I think most aren't.
>
> Maybe we should try to reduce subjectivity by getting more consensus on
> what issues are really important and which ones aren't.  That might get
> more consistency from the drive-bys.  But some of these issues are
> judgement calls and folks will have different opinions and podlings might
> be better served by being advised to get second opinions.
>
> Reducing the number of volunteers and holding them to a higher standard
> seems anti-volunteer.  It is why I've never asked to join the IPMC.   I can
> pound a nail and fix a flat tire, though.  Finding ways to reduce the size
> of the tasks and requirements on the timing seems like it would attract
> more volunteers and be more helpful.  Instead of having to review an entire
> release in order to cast a binding vote on it, maybe I could spend 5
> minutes to just run RAT on it and if it finds a binary, open a ticket
> asking why.
>
> HTH,
> -Alex
>
> On 3/2/19, 3:55 AM, "Greg Stein"  wrote:
>
> On Sat, Mar 2, 2019 at 5:17 AM sebb  wrote:
>
> > On Sat, 2 Mar 2019 at 10:49, Greg Stein  wrote:
> > >
> > > On Sat, Mar 2, 2019 at 2:50 AM sebb  wrote:
> > >
> > > > On Sat, 2 Mar 2019 at 03:45, Justin Mclean <
> jus...@classsoftware.com>
> > > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > > I agree that it's not ideal but it is not a symptom of a big
> > problem
> > > > either. We have inactive IPMC members who might become active
> again
> > later
> > > > if a community wants to join the incubator but it's a hassle to
> leave
> > and
> > > > then join again.
> > > > >
> > > > > Some context, over 300 projects have gone through the
> incubator, 50
> > are
> > > > there currently, each requires a champion and 3 mentors at the
> start
> > (all
> > > > IPMC members), even with some mentors working on multiple
> podling it's
> > not
> > > > surprising the IPMC is 300 people or so. Nor should it be that a
> large
> > > > number of them are inactive as most of the projects they were
> involved
> > in
> > > > have graduated (or retired).
> > > >
> > > > +1
> > > >
> > > > > But despite this some still think it is an issue so we IMO we
> should
> > > > address it, unless they change their minds, and say so here.
> > > >
> > > > Personally, I don't think that is a reason to reduce the IPMC
> count.
> > > > I think it needs to be established WHY it is thought to be an
> issue
> > first.
> > > >
> > >
> > > It encourages drive-by bikeshedding. "I'm an IPMC Member from a
> few years
> > > back. I see $foo, and OMG need to comment on it."
> > >
> > > Did anybody stop and read the concerns recently raised to the
> Board? Much
> > > of the focus on that email was about such drive-by commenting.
> > >
> > > 

Re: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates

[Thomas Weise]

I would consider it a mentor responsibility, just like any other advise on
the way towards graduation. There could be explicit mention in the maturity
assessment / checklist.

--
sent from mobile

On Tue, Feb 26, 2019, 11:33 PM Justin Mclean 
wrote:

> Hi,
>
> > But my proposal to move towards offering early feedback on
> > releases works with or without this change.
>
> +1
>
> How do we make podling aware they can do this? Obvious people who follow
> this list may know, and we can ask mentors to pass it on to their podling
> lists, on document on the website and perhaps mention it in Dave’s welcome
> package idea. But would that be enough?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Training into the Apache Incubator

[Thomas Weise]

+1 (binding)


On Wed, Feb 13, 2019, 6:40 AM Mohammad Asif Siddiqui 
wrote:

> +1 (binding)
>
> Regards
> Asif
>
> On Wed, Feb 13, 2019 at 8:09 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
> > +1 (non-binding)
> > I really liked the idea from the start and probably will find some time
> to
> > contribute!
> >
> > Julian
> >
> > Am 13.02.19, 15:18 schrieb "Kevin A. McGrail" :
> >
> > +1 Binding.  I'll also try again to get  Udacity, Udemy, Coursera,
> > Pluralsight involved now that this is going to a formal incubator
> > podling.
> > I am hoping once a domino falls, more will help.
> >
> > Regards,
> > KAM
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Wed, Feb 13, 2019 at 7:00 AM Vinayakumar B <
> vinayakum...@apache.org
> > >
> > wrote:
> >
> > > +1 (binding)
> > >
> > > -Vinay
> > >
> > >
> > > On Wed, Feb 13, 2019 at 4:58 PM Hans-Peter Zorn 
> > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Looking forward to work on this!
> > > > Thanks,
> > > > Hans-Peter
> > > >
> > > > > Am 13.02.2019 um 08:57 schrieb Lars Francke <
> > lars.fran...@gmail.com>:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > we've discussed the proposal for the Training project in [1]
> and
> > [2].
> > > The
> > > > > proposal itself can be found on the wiki[3].
> > > > >
> > > > > According to the Incubator rules[4] I'd like to call a vote to
> > accept
> > > the
> > > > > new "Training" project as a podling in the Apache Incubator.
> > > > >
> > > > > A vote for accepting a new Apache Incubator podling is a
> > majority vote.
> > > > > Everyone is welcome to vote, only Incubator PMC member votes
> are
> > > binding.
> > > > > It would be helpful (but not required) if you could add a
> comment
> > > stating
> > > > > whether your vote is binding or non-binding.
> > > > >
> > > > > This vote will run for at least 72 hours (but I expect to keep
> > it open
> > > > for
> > > > > longer). Please VOTE as follows:
> > > > >
> > > > > [ ] +1 Accept Training into the Apache Incubator
> > > > > [ ] +0 Abstain
> > > > > [ ] -1 Do not accept Training into the Apache Incubator because
> > ...
> > > > >
> > > > > Thank you for everyone who decided to join in in the past
> > discussions!
> > > > > Lars
> > > > >
> > > > > [1] <
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > > > >>
> > > > >
> > > > > [2] <
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > > > >>
> > > > >
> > > > > [3] <
> https://wiki.apache.org/incubator/TrainingProposal#preview>
> > > > >
> > > > > [4] <
> > > > >
> > > >
> > >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > > > >>
> > > >
> > > >
> > > >
> > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
> >
> >
>

Re: [VOTE] Shut down unused/inactive incubator lists

[Thomas Weise]

+1

On Mon, Jan 21, 2019 at 11:23 AM  wrote:

> +1
>
> Thanks
> Sharan
>
> On 21. 01. 19 1:11, sebb wrote:
> > The following lists are all but inactive:
> >
> > announce@ Last post Jan 2008
> > android-interest@ Last post Mar 2011
> > dev@ - only general circulars
> > jaxws-tck@ (private) Last post 2012
> > projects@ Last post Jul 2011
> > user@ - only general circulars
> >
> > I think they should be shut down.
> >
> > Please vote so an Infra Jira can be raised to shut them down.
> > They can have a bounce message added to direct posters to
> > general@/private@ as appropriate
> >
> > [  ] +1
> > [  ] -1 - give a reason please
> >
> > Please vote by end January 2019
> >
> > Sebb.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT] [VOTE] Accept Hudi into the Apache Incubator

[Thomas Weise]

The vote for accepting Hudi into the Apache Incubator passes with 11
binding +1 votes, 5 non-binding +1 votes and no other votes.

Thanks for voting!

+1 votes:

Luciano Resende*
Pierre Smits
Suneel Marthi*
Felix Cheung*
Kenneth Knowles*
Mohammad Islam
Mayank Bansal
Jakob Homan*
Akira Ajisaka*
Gosling Von*
Matt Sicker*
Brahma Reddy Battula
Hongtao Gao
Vinayakumar B*
Furkan Kamaci*
Thomas Weise*

* = binding


On Sun, Jan 13, 2019 at 2:34 PM Thomas Weise  wrote:

> Hi all,
>
> Following the discussion of the Hudi proposal in [1], this is a vote
> on accepting Hudi into the Apache Incubator,
> per the ASF policy [2] and voting rules [3].
>
> A vote for accepting a new Apache Incubator podling is a
> majority vote. Everyone is welcome to vote, only
> Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as
> follows:
>
> [ ] +1 Accept Hudi into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Hudi into the Apache Incubator because ...
>
> The proposal is included below, but you can also access it on
> the wiki [4].
>
> Thanks for reviewing and voting,
> Thomas
>
> [1]
> https://lists.apache.org/thread.html/12e2bdaa095d68dae6f8731e473d3d43885783177d1b7e3ff2f65b6d@%3Cgeneral.incubator.apache.org%3E
>
> [2]
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
>
> [3] http://www.apache.org/foundation/voting.html
>
> [4] https://wiki.apache.org/incubator/HudiProposal
>
>
>
> = Hudi Proposal =
>
> == Abstract ==
>
> Hudi is a big-data storage library, that provides atomic upserts and
> incremental data streams.
>
> Hudi manages data stored in Apache Hadoop and other API compatible
> distributed file systems/cloud stores.
>
> == Proposal ==
>
> Hudi provides the ability to atomically upsert datasets with new values in
> near-real time, making data available quickly to existing query engines
> like Apache Hive, Apache Spark, & Presto. Additionally, Hudi provides a
> sequence of changes to a dataset from a given point-in-time to enable
> incremental data pipelines that yield greater efficiency & latency than
> their typical batch counterparts. By carefully managing number of files &
> sizes, Hudi greatly aids both query engines (e.g: always providing
> well-sized files) and underlying storage (e.g: HDFS NameNode memory
> consumption).
>
> Hudi is largely implemented as an Apache Spark library that reads/writes
> data from/to Hadoop compatible filesystem. SQL queries on Hudi datasets are
> supported via specialized Apache Hadoop input formats, that understand
> Hudi’s storage layout. Currently, Hudi manages datasets using a combination
> of Apache Parquet & Apache Avro file/serialization formats.
>
> == Background ==
>
> Apache Hadoop distributed filesystem (HDFS) & other compatible cloud
> storage systems (e.g: Amazon S3, Google Cloud, Microsoft Azure) serve as
> longer term analytical storage for thousands of organizations. Typical
> analytical datasets are built by reading data from a source (e.g: upstream
> databases, messaging buses, or other datasets), transforming the data,
> writing results back to storage, & making it available for analytical
> queries--all of this typically accomplished in batch jobs which operate in
> a bulk fashion on partitions of datasets. Such a style of processing
> typically incurs large delays in making data available to queries as well
> as lot of complexity in carefully partitioning datasets to guarantee
> latency SLAs.
>
> The need for fresher/faster analytics has increased enormously in the past
> few years, as evidenced by the popularity of Stream processing systems like
> Apache Spark, Apache Flink, and messaging systems like Apache Kafka. By
> using updateable state store to incrementally compute & instantly reflect
> new results to queries and using a “tailable” messaging bus to publish
> these results to other downstream jobs, such systems employ a different
> approach to building analytical dataset. Even though this approach yields
> low latency, the amount of data managed in such real-time data-marts is
> typically limited in comparison to the aforementioned longer term storage
> options. As a result, the overall data architecture has become more complex
> with more moving parts and specialized systems, leading to duplication of
> data and a strain on usability.
>
> Hudi takes a hybrid approach. Instead of moving vast amounts of batch data
> to streaming systems, we simply add the streaming primitives (upserts &
> incremental consumption) onto existing batch processing technologies. We
> believe that by adding some missing blocks to an existing Hadoop stack, we
> are able 

Re: [VOTE] Accept Hudi into the Apache Incubator

[Thomas Weise]

+1


On Wed, Jan 16, 2019 at 11:35 AM Matt Sicker  wrote:

> +1
>
> On Wed, 16 Jan 2019 at 01:25, Gosling Von  wrote:
> >
> > +1(binding)
> >
> > Best Regards,
> > Von Gosling
> >
> > > 在 2019年1月14日，上午6:34，Thomas Weise  写道：
> > >
> > > Hi all,
> > >
> > > Following the discussion of the Hudi proposal in [1], this is a vote
> > > on accepting Hudi into the Apache Incubator,
> > > per the ASF policy [2] and voting rules [3].
> > >
> > > A vote for accepting a new Apache Incubator podling is a
> > > majority vote. Everyone is welcome to vote, only
> > > Incubator PMC member votes are binding.
> > >
> > > This vote will run for at least 72 hours. Please VOTE as
> > > follows:
> > >
> > > [ ] +1 Accept Hudi into the Apache Incubator
> > > [ ] +0 Abstain
> > > [ ] -1 Do not accept Hudi into the Apache Incubator because ...
> > >
> > > The proposal is included below, but you can also access it on
> > > the wiki [4].
> > >
> > > Thanks for reviewing and voting,
> > > Thomas
> > >
> > > [1]
> > >
> https://lists.apache.org/thread.html/12e2bdaa095d68dae6f8731e473d3d43885783177d1b7e3ff2f65b6d@%3Cgeneral.incubator.apache.org%3E
> > >
> > > [2]
> > >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > >
> > > [3] http://www.apache.org/foundation/voting.html
> > >
> > > [4] https://wiki.apache.org/incubator/HudiProposal
> > >
> > >
> > >
> > > = Hudi Proposal =
> > >
> > > == Abstract ==
> > >
> > > Hudi is a big-data storage library, that provides atomic upserts and
> > > incremental data streams.
> > >
> > > Hudi manages data stored in Apache Hadoop and other API compatible
> > > distributed file systems/cloud stores.
> > >
> > > == Proposal ==
> > >
> > > Hudi provides the ability to atomically upsert datasets with new
> values in
> > > near-real time, making data available quickly to existing query engines
> > > like Apache Hive, Apache Spark, & Presto. Additionally, Hudi provides a
> > > sequence of changes to a dataset from a given point-in-time to enable
> > > incremental data pipelines that yield greater efficiency & latency than
> > > their typical batch counterparts. By carefully managing number of
> files &
> > > sizes, Hudi greatly aids both query engines (e.g: always providing
> > > well-sized files) and underlying storage (e.g: HDFS NameNode memory
> > > consumption).
> > >
> > > Hudi is largely implemented as an Apache Spark library that
> reads/writes
> > > data from/to Hadoop compatible filesystem. SQL queries on Hudi
> datasets are
> > > supported via specialized Apache Hadoop input formats, that understand
> > > Hudi’s storage layout. Currently, Hudi manages datasets using a
> combination
> > > of Apache Parquet & Apache Avro file/serialization formats.
> > >
> > > == Background ==
> > >
> > > Apache Hadoop distributed filesystem (HDFS) & other compatible cloud
> > > storage systems (e.g: Amazon S3, Google Cloud, Microsoft Azure) serve
> as
> > > longer term analytical storage for thousands of organizations. Typical
> > > analytical datasets are built by reading data from a source (e.g:
> upstream
> > > databases, messaging buses, or other datasets), transforming the data,
> > > writing results back to storage, & making it available for analytical
> > > queries--all of this typically accomplished in batch jobs which
> operate in
> > > a bulk fashion on partitions of datasets. Such a style of processing
> > > typically incurs large delays in making data available to queries as
> well
> > > as lot of complexity in carefully partitioning datasets to guarantee
> > > latency SLAs.
> > >
> > > The need for fresher/faster analytics has increased enormously in the
> past
> > > few years, as evidenced by the popularity of Stream processing systems
> like
> > > Apache Spark, Apache Flink, and messaging systems like Apache Kafka. By
> > > using updateable state store to incrementally compute & instantly
> reflect
> > > new results to queries and using a “tailable” messaging bus to publish
> > > these results to other downstream jobs, such systems employ a different
> > > approach to building analytical

[VOTE] Accept Hudi into the Apache Incubator

[Thomas Weise]

and technical
elements and we will highlight them here. Hive ACID/Kudu both offer upsert
capabilities without storage management/incremental streams. The recent
Iceberg project offers similar snapshot isolation/rollbacks, but not
upserts or other data plane features. A detailed comparison with their
trade-offs can be found at https://uber.github.io/hudi/comparison.html.

We are committed to open collaboration with such Apache projects and
incorporate changes to Hudi or contribute patches to other projects, with
the goal of making it easier for the community at large, to adopt these
open source technologies.

=== Excessive Fascination with the Apache Brand ===

This proposal is not for the purpose of generating publicity. We have
already been doing talks/meetups independently that have helped us build
our community. We are drawn towards Apache as a potential way of ensuring
that our open source community management is successful early on so  hudi
can evolve into a broadly accepted--and used--method of managing data on
Hadoop.

== Documentation ==
[1] Detailed documentation can be found at https://uber.github.io/hudi/

== Initial Source ==

The codebase is currently hosted on Github: https://github.com/uber/hudi .
During incubation, the codebase will be migrated to an Apache
infrastructure. The source code already has an Apache 2.0 licensed.

== Source and Intellectual Property Submission Plan ==

Current code is Apache 2.0 licensed and the copyright is assigned to Uber.
If the project enters incubator, Uber will transfer the source code &
trademark ownership to ASF via a Software Grant Agreement

== External Dependencies ==

Non apache dependencies are listed below

 * JCommander (1.48) Apache-2.0
 * Kryo (4.0.0) BSD-2-Clause
 * Kryo (2.21) BSD-3-Clause
 * Jackson-annotations (2.6.4) Apache-2.0
 * Jackson-annotations (2.6.5) Apache-2.0
 * jackson-databind (2.6.4) Apache-2.0
 * jackson-databind (2.6.5) Apache-2.0
 * Jackson datatype: Guava (2.9.4) Apache-2.0
 * docker-java (3.1.0-rc-3) Apache-2.0
 * Guava: Google Core Libraries for Java (20.0) Apache-2.0
 * bijection-avro (0.9.2) Apache-2.0
 * com.twitter.common:objectsize (0.0.12) Apache-2.0
 * Ascii Table (0.2.5) Apache-2.0
 * config (3.0.0) Apache-2.0
 * utils (3.0.0) Apache-2.0
 * kafka-avro-serializer (3.0.0) Apache-2.0
 * kafka-schema-registry-client (3.0.0) Apache-2.0
 * Metrics Core (3.1.1) Apache-2.0
 * Graphite Integration for Metrics (3.1.1) Apache-2.0
 * Joda-Time (2.9.6) Apache-2.0
 * JUnit CPL-1.0
 * Awaitility (3.1.2) Apache-2.0
 * jersey-connectors-apache (2.17) GPL-2.0-only CDDL-1.0
 * jersey-container-servlet-core (2.17) GPL-2.0-only CDDL-1.0
 * jersey-core-server (2.17) GPL-2.0-only CDDL-1.0
 * htrace-core (3.0.4) Apache-2.0
 * Mockito (1.10.19) MIT
 * scalatest (3.0.1) Apache-2.0
 * Spring Shell (1.2.0.RELEASE) Apache-2.0

All of them are Apache compatible

== Cryptography ==

No cryptographic libraries used

== Required Resources ==

=== Mailing lists ===

 * priv...@hudi.incubator.apache.org (with moderated subscriptions)
 * d...@hudi.incubator.apache.org
 * comm...@hudi.incubator.apache.org
 * u...@hudi.incubator.apache.org

=== Git Repositories ===

Git is the preferred source control system: git://
git.apache.org/incubator-hudi

=== Issue Tracking ===

We prefer to use the Apache gitbox integration to sync Github & Apache
infrastructure, and rely on Github issues & pull requests for community
engagement. If this is not possible, then we prefer JIRA: Hudi (HUDI)

== Initial Committers ==

 * Vinoth Chandar (vinoth at uber dot com) (Uber)
 * Nishith Agarwal (nagarwal at uber dot com) (Uber)
 * Balaji Varadarajan (varadarb at uber dot com) (Uber)
 * Prasanna Rajaperumal (prasanna dot raj at gmail dot com) (Snowflake)
 * Zeeshan Qureshi (zeeshan dot qureshi at shopify dot com) (Shopify)
 * Anbu Cheeralan (alunarbeach at gmail dot com) (DoubleVerify)

== Sponsors ==

=== Champion ===
Julien Le Dem (julien at apache dot org)

=== Nominated Mentors ===

 * Luciano Resende (lresende at apache dot org)
 * Thomas Weise (thw at apache dot org
 * Kishore Gopalakrishna (kishoreg at apache dot org)
 * Suneel Marthi (smarthi at apache dot org)

=== Sponsoring Entity ===

The Incubator PMC

Re: [DISCUSS] Hudi Incubation Proposal

[Thomas Weise]

I will start the VOTE in a day or two if there are no further comments.


On Fri, Jan 11, 2019 at 2:59 PM Vinoth Chandar 
wrote:

> Hi all,
>
> Added Suneel Marthi as another mentor to the project. Thanks Suneel!
>
> Thanks
> Vinoth
>
> On Fri, Jan 11, 2019 at 8:09 AM Thomas Weise  wrote:
>
> > I think that's a fair point.
> >
> > If we can make sure we have one more experienced mentor with sufficient
> > time commitment for at least advisory capacity.
> >
> > I'm happy to pick up more of the legwork for initial setup etc.
> >
> > Thomas
> >
> > On Thu, Jan 10, 2019 at 7:48 PM Justin Mclean 
> wrote:
> >
> > > Hi,
> > >
> > > While I would not oppose it going forward I think the podling could
> still
> > > do with another experienced mentor. Any takers?
> > >
> > > Reason why I think this is below, please don’t take this personally or
> if
> > > you think it’s inaccurate speak up, I just want to give this new
> podling
> > a
> > > good chance at success..
> > >
> > > > * Luciano Resende (lresende at apache dot org)
> > >
> > > Experienced mentor, but may have a few too many podlings to be able to
> > > spend a lot of time mentoring this podling.
> > >
> > > > * Thomas Weise (thw at apache dot org
> > >
> > > First time mentor and new IPMC member.
> > >
> > > > * Kishore Gopalakrishna (kishoreg at apache dot org)
> > >
> > >
> > > First time mentor and new IPMC member.who not been that active.
> (Podling
> > > missed report and missed last report missed signoff).
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Hudi Incubation Proposal

[Thomas Weise]

I think that's a fair point.

If we can make sure we have one more experienced mentor with sufficient
time commitment for at least advisory capacity.

I'm happy to pick up more of the legwork for initial setup etc.

Thomas

On Thu, Jan 10, 2019 at 7:48 PM Justin Mclean  wrote:

> Hi,
>
> While I would not oppose it going forward I think the podling could still
> do with another experienced mentor. Any takers?
>
> Reason why I think this is below, please don’t take this personally or if
> you think it’s inaccurate speak up, I just want to give this new podling a
> good chance at success..
>
> > * Luciano Resende (lresende at apache dot org)
>
> Experienced mentor, but may have a few too many podlings to be able to
> spend a lot of time mentoring this podling.
>
> > * Thomas Weise (thw at apache dot org
>
> First time mentor and new IPMC member.
>
> > * Kishore Gopalakrishna (kishoreg at apache dot org)
>
>
> First time mentor and new IPMC member.who not been that active. (Podling
> missed report and missed last report missed signoff).
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Hudi Incubation Proposal

[Thomas Weise]

Very exciting to see this proposal!


On Thu, Dec 20, 2018 at 2:20 PM Sid Anand  wrote:

> Looks great Vinoth!
> -s (Sid)
>
> On Thu, Dec 20, 2018 at 11:42 AM Vinoth Chandar 
> wrote:
>
> > I have created the proposal in the incubator wiki
> > https://wiki.apache.org/incubator/HudiProposal
> >
> >
> > On Thu, Dec 20, 2018 at 6:04 AM Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> > > On Thu, Dec 20, 2018 at 2:51 PM Vinoth Chandar  >
> > > wrote:
> > > > Created. Username:vinothchandar
> > >
> > > ok, you should have access now.
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Apache Apex Core Release 3.2.1-incubating (RC1)

[Thomas Weise]

Dear IPMC members,

One more nod for this release please.

Thanks,
Thomas


On Tue, Apr 19, 2016 at 2:13 PM, Vlad Rozov  wrote:

> Hi IPMC members,
>
> With 2 +1 binding votes from Justin and Alan, we need one more vote to
> proceed with the release. May I ask for one more check and vote on the RC1.
>
> Staging directory:
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.1-incubating-RC1
> Source zip:
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.1-incubating-RC1/apex-3.2.1-incubating-source-release.zip
> Source tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.1-incubating-RC1/apex-3.2.1-incubating-source-release.tar.gz
> Maven staging repository:
> https://repository.apache.org/content/repositories/orgapacheapex-1011
>
> Git source:
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.2.1-incubating-RC1
> (commit: 8481c128896091013c5f62a2f25bcb15fe9f6a3f)
>
> PGP key:
> http://pgp.mit.edu:11371/pks/lookup?op=vindex=vro...@apache.org
> KEYS file: https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
>
> Thank you,
>
> Vlad
>
>
>
> On 4/18/16 14:57, Alan Gates wrote:
>
>> +1, checked LICENSE, NOTICE, and DISCLAIMER files.  Checked that no
>> binaries are present.  Checked the signatures.
>>
>> Alan.
>>
>> On Apr 17, 2016, at 15:01, Justin Mclean 
>>> wrote:
>>>
>>> Hi,
>>>
>>> +1 binding - carried over form dev list all of the usual checks done.
>>>
>>> Thanks,
>>> Justin
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Apex Core Release 3.2.1-incubating (RC1)

[Thomas Weise]

+1 carried over from dev@

Thomas


On Sun, Apr 17, 2016 at 3:01 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 binding - carried over form dev list all of the usual checks done.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apex from the Incubator

[Thomas Weise]

+1

Thanks,
Thomas

On Mon, Mar 28, 2016 at 2:46 PM, Pramod Immaneni <pra...@datatorrent.com>
wrote:

> Sorry missed including the resolution. Here is the full email again..
>
> The Apache Apex community has discussed and voted on graduation to top
> level project.
> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
>
> Maturity Assessment:http://apex.incubator.apache.org/maturity.html
> Discussion:https://s.apache.org/qrvY
> Vote:https://s.apache.org/R8MR
> Result:https://s.apache.org/sJIC
>
> Please vote on the resolution pasted below to graduate Apache Apex
> from the incubator to top level project.
>
> [ ] +1 Graduate Apache Apex from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Apex from the Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
>
> Pramod Immaneni, for the Apache Apex PPMC
>
>
>
> Apache Apex top-level project resolution:
> =
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to Hadoop native, distributed,
> large-scale, high throughput, low-latency, fault tolerant,
> easily operable, unified stream and batch processing platform.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Apex Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Apex Project be and hereby is
> responsible for the creation and maintenance of software
> related to Hadoop native, distributed, large-scale,
> high throughput, low-latency, fault tolerant, easily operable,
> unified stream and batch processing platform;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache Apex" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Apex Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Apex Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Apex Project:
>
> * Ilya Ganelin <ilgan...@apache.org>
> * P. Taylor Goetz <ptgo...@apache.org>
> * Gaurav Gupta <gauravgopi...@apache.org>
> * Pramod Immaneni <pra...@apache.org>
> * Amol Kekre <ake...@apache.org>
> * Justin Mclean <jmcl...@apache.org>
> * Chetan Narsude <che...@apache.org>
> * Chris Nauroth <cnaur...@apache.org>
> * Vlad Rozov <vro...@apache.org>
> * Hitesh Shah <hit...@apache.org>
> * Thomas Weise <t...@apache.org>
> * David Yan <david...@apache.org>
> * Brennon York <boy...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
> be appointed to the office of Vice President, Apache Apex, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Apex PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Apex Project; and be it further
>
> RESOLVED, that the Apache Apex Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Apex podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Apex podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning <ted.dunn...@gmail.com>
> wrote:
>
> > There hasn't been a discussion thread here on the general list, but I am
> > still prepared to vote in favor of this.
> >
> > +1
> >
> > See!
> >
> > I just did.
> >
> >
> >
> > On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni <pra...@apache.org>
> > wrote:
> >
> > > The Apache Apex community has discussed and voted on graduation to top
> > > level project.
> > > The vote passed with 42 +1 votes (12 from the PPMC) and 

Fwd: [VOTE] Graduate Apex from the Incubator

[Thomas Weise]

Please note that a graduation community [VOTE] is in progress for Apache
Apex.

Thanks,
Thomas

-- Forwarded message --
From: Pramod Immaneni <pra...@apache.org>
Date: Tue, Mar 22, 2016 at 10:36 AM
Subject: [VOTE] Graduate Apex from the Incubator
To: d...@apex.incubator.apache.org


Dear Community,

Based on the positive discussion, I'm calling for the community VOTE
to graduate Apache Apex (incubating) to top level project (TLP).

Please vote on the resolution pasted below.

[ ] +1 Graduate Apache Apex from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Apex from the Incubator because…

This is a community vote and everyone is invited to participate. PPMC
votes should be marked binding.

This vote will be open for at least 72 hours.

If this VOTE succeeds, a similar VOTE will commence on the
general@incubator mailing list. If that vote also succeeds,
we will submit the resolution to be included in the agenda
of the next Apache board meeting.

Many thanks to our mentors and everyone else for the support,

Pramod, for the Apache Apex PPMC

My vote is +1 (binding)

Apache Apex top-level project resolution:
=

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to Hadoop native, distributed,
large-scale, high throughput, low-latency, fault tolerant,
easily operable, unified stream and batch processing platform.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Apex Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Apex Project be and hereby is
responsible for the creation and maintenance of software
related to Hadoop native, distributed, large-scale,
high throughput, low-latency, fault tolerant, easily operable,
unified stream and batch processing platform;
and be it further

RESOLVED, that the office of "Vice President, Apache Apex" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Apex Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Apex Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Apex Project:

* Ilya Ganelin <ilgan...@apache.org>
* P. Taylor Goetz <ptgo...@apache.org>
* Gaurav Gupta <gauravgopi...@apache.org>
* Pramod Immaneni <pra...@apache.org>
* Amol Kekre <ake...@apache.org>
* Justin Mclean <jmcl...@apache.org>
* Chetan Narsude <che...@apache.org>
* Chris Nauroth <cnaur...@apache.org>
* Vlad Rozov <vro...@apache.org>
* Hitesh Shah <hit...@apache.org>
* Thomas Weise <t...@apache.org>
* David Yan <david...@apache.org>
* Brennon York <boy...@apache.org>

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
be appointed to the office of Vice President, Apache Apex, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Apex PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Apex Project; and be it further

RESOLVED, that the Apache Apex Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Apex podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Apex podling encumbered upon the Apache Incubator
Project are hereafter discharged.

[ANNOUNCE] Apache Apex Core 3.3.0-incubating released

[Thomas Weise]

The Apache Apex community is pleased to announce release 3.3.0-incubating
(Apex Core).

Changes:
https://github.com/apache/incubator-apex-core/blob/v3.3.0-incubating/CHANGELOG.md

Apache Apex is an enterprise grade native YARN big data-in-motion platform
that unifies stream and batch processing. Apex was built for scalability
and low-latency processing, high availability and operability.

This release adds exciting new features, including support for iterative
processing, modules (ability to expand building blocks into subgraph of
lower level operators), new callback to perform custom operator logic to
optimize checkpointing and more.

This is a source release with binary artifacts published to Maven. The
source release can be found at:

http://www.apache.org/dyn/closer.lua/incubator/apex/v3.3.0-incubating/apex-3.3.0-incubating-source-release.tar.gz

or visit:

http://apex.incubator.apache.org/downloads.html

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at:

http://apex.incubator.apache.org/

Regards,
The Apache Apex community


Disclaimer:
Apache Apex is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

[RESULT] [VOTE] Release Apache Apex Core 3.3.0-incubating (RC2)

[Thomas Weise]

The vote passes with 4, +1 binding votes from IPMC members and no -1s:

Justin Mclean
Alan Gates
Chris Nauroth
Hitesh Shah

Thanks for voting, we will proceed with the release activities.

Thomas

On Thu, Feb 4, 2016 at 10:49 AM, Hitesh Shah <hit...@apache.org> wrote:

> +1 (binding) - carried over from dev vote.
>
> — Hitesh
>
> On Feb 4, 2016, at 12:36 AM, Thomas Weise <t...@apache.org> wrote:
>
> > Hi,
> >
> > Please vote on the following Apache Apex Core 3.3.0-incubating release
> > candidate.
> >
> > The Apache Apex PPMC has voted to release this candidate.
> >
> > The community vote passed with 5 binding votes from the PPMC (including 3
> > votes from IPMC members). There were another 11 committer votes in favor
> of
> > the release.
> >
> > PPMC vote call:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDPjMAZc8-NjjyMgtJGDpHkhVpxv8PYnryfiF4zZZufVmA%40mail.gmail.com%3E
> >
> > PPMC vote result:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDN4CUVn9cgVhAhqeojP4hDUhwjnWRgXD226VOOBPphmUg%40mail.gmail.com%3E
> >
> > This is a source release with binary artifacts published to Maven.
> >
> > List of all issues fixed: http://s.apache.org/wUB
> >
> > Staging directory:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2
> > Source zip:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.zip
> > Source tar.gz:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.tar.gz
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheapex-1006/
> >
> > Git source:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.3.0-incubating-RC2
> > (commit: 5f216a1bd27a94785c9ccada78101f892be95cbe)
> >
> > PGP key:
> > http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> > KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >
> > More information at:
> > http://apex.incubator.apache.org
> >
> > Please try the release and vote; vote will be open for at least 72 hours.
> >
> > Thanks,
> > Thomas
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Apache Apex Core 3.3.0-incubating (RC2)

[Thomas Weise]

Hi,

Please vote on the following Apache Apex Core 3.3.0-incubating release
candidate.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 5 binding votes from the PPMC (including 3
votes from IPMC members). There were another 11 committer votes in favor of
the release.

PPMC vote call:
http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDPjMAZc8-NjjyMgtJGDpHkhVpxv8PYnryfiF4zZZufVmA%40mail.gmail.com%3E

PPMC vote result:
http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDN4CUVn9cgVhAhqeojP4hDUhwjnWRgXD226VOOBPphmUg%40mail.gmail.com%3E

This is a source release with binary artifacts published to Maven.

List of all issues fixed: http://s.apache.org/wUB

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1006/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.3.0-incubating-RC2
 (commit: 5f216a1bd27a94785c9ccada78101f892be95cbe)

PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org

Please try the release and vote; vote will be open for at least 72 hours.

Thanks,
Thomas

[ANNOUNCE] Apache Apex Malhar Release 3.3.0-incubating released

[Thomas Weise]

The Apache Apex community is pleased to announce release 3.3.0-incubating
of the Malhar Library.

Changes:
https://github.com/apache/incubator-apex-malhar/blob/v3.3.0-incubating/CHANGELOG.md

Apache Apex is an enterprise grade native YARN big data-in-motion platform
that unifies stream processing and batch processing. Apex was built for
scalability and low-latency processing, high availability and operability.

Apache Apex is Java based and strives to ease application development on a
platform that takes care of aspects such as stateful fault tolerance,
partitioning, processing guarantees, buffering and synchronization,
auto-scaling etc. Apex comes with Malhar, a rich library of pre-built
operators, including adapters that integrate with existing technologies as
sources and destinations, like message buses, databases, files or social
media feeds.

The source release can be found at:

http://www.apache.org/dyn/closer.lua/incubator/apex/malhar/v3.3.0-incubating/malhar-3.3.0-incubating-source-release.tar.gz

or visit:

http://apex.incubator.apache.org/downloads.html

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at:

http://apex.incubator.apache.org/

Regards,
The Apache Apex community


Disclaimer:
Apache Apex is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

[RESULT][VOTE] Apache Apex Malhar Release 3.3.0-incubating (RC1)

[Thomas Weise]

The vote passes with 3, +1 binding votes from IPMC members and no -1s:

Justin Mclean
P. Taylor Goetz
Chris Nauroth

Thanks for voting, we will proceed with the release activities.

Thomas

On Sun, Jan 17, 2016 at 2:00 PM, Chris Nauroth <cnaur...@hortonworks.com>
wrote:

> +1 (binding)
>
> - Verified signatures.
> - Verified hashes.
> - DISCLAIMER, LICENSE and NOTICE all look good.
> - Reviewed sample of source files for license header, and they look good.
> - Ran mvn install to build and run tests successfully.
>
>
> --Chris Nauroth
>
>
>
>
> On 1/15/16, 6:33 PM, "Thomas Weise" <thomas.we...@gmail.com> wrote:
>
> >Thanks to everyone who voted so far. We need one more binding +1 to wrap
> >it
> >up please :-)
> >
> >Thomas
> >
> >On Thu, Jan 14, 2016 at 3:34 PM, P. Taylor Goetz <ptgo...@gmail.com>
> >wrote:
> >
> >> +1 (binding)
> >>
> >> Licensing looks good, can build forms source, and the signatures check
> >>out.
> >>
> >> -Taylor
> >>
> >> > On Jan 12, 2016, at 10:35 PM, Thomas Weise <t...@apache.org> wrote:
> >> >
> >> > Hi,
> >> >
> >> > Please vote on the following Apache Apex Mahar 3.3.0-incubating
> >>release
> >> > candidate.
> >> >
> >> > The Apache Apex PPMC has voted to release this candidate.
> >> >
> >> > The community vote passed with 4 binding votes from the PPMC
> >>(including 1
> >> > vote from IPMC members). There were another 6 committer votes in
> >>favor of
> >> > the release.
> >> >
> >> > PPMC vote call:
> >> >
> >> >
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%
> >>3CCAKJfLDOj58dtfWTw2oBfm5GsyZqsbWCYFSCro9U%2BJw2%2BTFbVpQ%
> 40mail.gmail.co
> >>m%3E
> >> >
> >> > PPMC vote result:
> >> >
> >> >
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%
> >>3CCAKJfLDMcv9n%3DvNneYBYGV%3DrDLpDcEn8eAVkbfbD6WznJdFZFKA%
> 40mail.gmail.co
> >>m%3E
> >> >
> >> >
> >> > List of all issues fixed: http://s.apache.org/8uT
> >> >
> >> > Staging directory:
> >> >
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incub
> >>ating-RC1
> >> > Source zip:
> >> >
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incub
> >>ating-RC1/malhar-3.3.0-incubating-source-release.zip
> >> > Source tar.gz:
> >> >
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incub
> >>ating-RC1/malhar-3.3.0-incubating-source-release.tar.gz
> >> > Maven staging repository:
> >> >
> https://repository.apache.org/content/repositories/orgapacheapex-1004/
> >> >
> >> > Git source:
> >> >
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=com
> >>mit;h=refs/tags/v3.3.0-incubating-RC1
> >> > (commit: ce2ac6edecd59e3f75fc5341b061c219a87292d2)
> >> >
> >> > PGP key:
> >> > http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> >> > KEYS file:
> >> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >> >
> >> > More information at:
> >> > http://apex.incubator.apache.org
> >> >
> >> > Please try the release and vote; vote will be open for at least 72
> >>hours.
> >> >
> >> > Thanks,
> >> > Thomas
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Apex Malhar Release 3.3.0-incubating (RC1)

[Thomas Weise]

Thanks but our votes are not binding in the IPMC vote thread.


On Fri, Jan 15, 2016 at 9:20 PM, Gaurav Gupta <gau...@datatorrent.com>
wrote:

> +1 (binding) Carried over from dev list
>
> Thanks
> - Gaurav
>
> > On Jan 15, 2016, at 6:33 PM, Thomas Weise <thomas.we...@gmail.com>
> wrote:
> >
> > Thanks to everyone who voted so far. We need one more binding +1 to wrap
> it
> > up please :-)
> >
> > Thomas
> >
> > On Thu, Jan 14, 2016 at 3:34 PM, P. Taylor Goetz <ptgo...@gmail.com>
> wrote:
> >
> >> +1 (binding)
> >>
> >> Licensing looks good, can build forms source, and the signatures check
> out.
> >>
> >> -Taylor
> >>
> >>> On Jan 12, 2016, at 10:35 PM, Thomas Weise <t...@apache.org> wrote:
> >>>
> >>> Hi,
> >>>
> >>> Please vote on the following Apache Apex Mahar 3.3.0-incubating release
> >>> candidate.
> >>>
> >>> The Apache Apex PPMC has voted to release this candidate.
> >>>
> >>> The community vote passed with 4 binding votes from the PPMC
> (including 1
> >>> vote from IPMC members). There were another 6 committer votes in favor
> of
> >>> the release.
> >>>
> >>> PPMC vote call:
> >>>
> >>>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDOj58dtfWTw2oBfm5GsyZqsbWCYFSCro9U%2BJw2%2BTFbVpQ%40mail.gmail.com%3E
> >>>
> >>> PPMC vote result:
> >>>
> >>>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDMcv9n%3DvNneYBYGV%3DrDLpDcEn8eAVkbfbD6WznJdFZFKA%40mail.gmail.com%3E
> >>>
> >>>
> >>> List of all issues fixed: http://s.apache.org/8uT
> >>>
> >>> Staging directory:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1
> >>> Source zip:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.zip
> >>> Source tar.gz:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.tar.gz
> >>> Maven staging repository:
> >>> https://repository.apache.org/content/repositories/orgapacheapex-1004/
> >>>
> >>> Git source:
> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.3.0-incubating-RC1
> >>> (commit: ce2ac6edecd59e3f75fc5341b061c219a87292d2)
> >>>
> >>> PGP key:
> >>> http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> >>> KEYS file:
> >>> https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >>>
> >>> More information at:
> >>> http://apex.incubator.apache.org
> >>>
> >>> Please try the release and vote; vote will be open for at least 72
> hours.
> >>>
> >>> Thanks,
> >>> Thomas
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>

Re: [VOTE] Apache Apex Malhar Release 3.3.0-incubating (RC1)

[Thomas Weise]

Thanks to everyone who voted so far. We need one more binding +1 to wrap it
up please :-)

Thomas

On Thu, Jan 14, 2016 at 3:34 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:

> +1 (binding)
>
> Licensing looks good, can build forms source, and the signatures check out.
>
> -Taylor
>
> > On Jan 12, 2016, at 10:35 PM, Thomas Weise <t...@apache.org> wrote:
> >
> > Hi,
> >
> > Please vote on the following Apache Apex Mahar 3.3.0-incubating release
> > candidate.
> >
> > The Apache Apex PPMC has voted to release this candidate.
> >
> > The community vote passed with 4 binding votes from the PPMC (including 1
> > vote from IPMC members). There were another 6 committer votes in favor of
> > the release.
> >
> > PPMC vote call:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDOj58dtfWTw2oBfm5GsyZqsbWCYFSCro9U%2BJw2%2BTFbVpQ%40mail.gmail.com%3E
> >
> > PPMC vote result:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDMcv9n%3DvNneYBYGV%3DrDLpDcEn8eAVkbfbD6WznJdFZFKA%40mail.gmail.com%3E
> >
> >
> > List of all issues fixed: http://s.apache.org/8uT
> >
> > Staging directory:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1
> > Source zip:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.zip
> > Source tar.gz:
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.tar.gz
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheapex-1004/
> >
> > Git source:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.3.0-incubating-RC1
> > (commit: ce2ac6edecd59e3f75fc5341b061c219a87292d2)
> >
> > PGP key:
> > http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> > KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >
> > More information at:
> > http://apex.incubator.apache.org
> >
> > Please try the release and vote; vote will be open for at least 72 hours.
> >
> > Thanks,
> > Thomas
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache Apex Malhar Release 3.3.0-incubating (RC1)

[Thomas Weise]

Hi,

Please vote on the following Apache Apex Mahar 3.3.0-incubating release
candidate.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 4 binding votes from the PPMC (including 1
vote from IPMC members). There were another 6 committer votes in favor of
the release.

PPMC vote call:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDOj58dtfWTw2oBfm5GsyZqsbWCYFSCro9U%2BJw2%2BTFbVpQ%40mail.gmail.com%3E

PPMC vote result:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201601.mbox/%3CCAKJfLDMcv9n%3DvNneYBYGV%3DrDLpDcEn8eAVkbfbD6WznJdFZFKA%40mail.gmail.com%3E


List of all issues fixed: http://s.apache.org/8uT

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.3.0-incubating-RC1/malhar-3.3.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1004/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.3.0-incubating-RC1
 (commit: ce2ac6edecd59e3f75fc5341b061c219a87292d2)

PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org

Please try the release and vote; vote will be open for at least 72 hours.

Thanks,
Thomas

[ANNOUNCE] Apache Apex Malhar Release 3.2.0-incubating released

[Thomas Weise]

The Apache Apex community is pleased to announce release 3.2.0-incubating
of the Malhar Library.

Changes:
https://github.com/apache/incubator-apex-malhar/blob/v3.2.0-incubating/CHANGELOG.md

Apache Apex is an enterprise grade native YARN big data-in-motion platform
that unifies stream processing as well as batch processing. Apex was built
for scalability and low-latency processing, high availability and
operability.

Apache Apex is Java based and strives to ease application development on a
platform that takes care of aspects such as stateful fault tolerance,
partitioning, processing guarantees, buffering and synchronization,
auto-scaling etc. Apex comes with Malhar, a rich library of pre-built
operators, including adapters that integrate with existing technologies as
sources and destinations, like message buses, databases, files or social
media feeds.

The source release can be found at:

http://www.apache.org/dyn/closer.lua/incubator/apex/malhar/v3.2.0-incubating/malhar-3.2.0-incubating-source-release.tar.gz

or visit:

http://apex.incubator.apache.org/downloads.html

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at:

http://apex.incubator.apache.org/

Regards,
The Apache Apex community


Disclaimer:
Apache Apex is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

[RESULT][VOTE] Apache Apex Malhar Release 3.2.0-incubating (RC2)

[Thomas Weise]

The vote passes with 3, +1 binding votes from IPMC members and no -1s:

Justin Mclean
Hitesh Shah
Alan Gates

Thanks for voting, we will proceed with the release activities.

Thomas

On Mon, Nov 16, 2015 at 5:57 PM, Sasha Parfenov <sa...@datatorrent.com>
wrote:

> +1.  Carried over from Apache Apex (incubating) dev list vote.
>
> Thanks,
> Sasha
>
> On Mon, Nov 16, 2015 at 11:45 AM, Alan Gates <alanfga...@gmail.com> wrote:
>
>> +1, see dev vote thread for details of checking I did.
>>
>> Alan.
>>
>> Thomas Weise <t...@apache.org>
>> November 13, 2015 at 21:30
>> Hi,
>>
>> Please vote on the following Apache Apex Malhar 3.2.0-incubating release
>> candidate. This is the first release of the Malhar library in ASF and it
>> is
>> based on Apex core 3.2.0-incubating. This is a source release.
>>
>> The Apache Apex PPMC has voted to release this candidate.
>>
>> The community vote passed with 14 binding votes from the PPMC (including 3
>> votes from IPMC members).
>>
>> PPMC vote call:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDMWgzncdN7-nxXksE3F2p3xLfCu%2B_nNL-q6p-H_kwASdA%40mail.gmail.com%3E
>>
>> PPMC vote result:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDPnu2vJZyt%3D9JNmt3nG_nHYk%2B3AseE__SN%3DKXmJ5AskeQ%40mail.gmail.com%3E
>>
>> List of all issues fixed: http://s.apache.org/2fZ
>>
>> Staging directory:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2
>> Source zip:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.zip
>> Source tar.gz:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.tar.gz
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapacheapex-1003/
>>
>> Git source:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
>> (commit:
>> ff0b0d080ebd8d00cee47321df90dad9357bbead)
>>
>> PGP key:
>> http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
>> KEYS file:
>> https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
>>
>> More information at:
>> http://apex.incubator.apache.org
>>
>> Please try the release and vote; vote will close after 72 hours.
>>
>> [ ] +1 approve
>> [ ] -1 disapprove (and reason why)
>>
>> http://www.apache.org/foundation/voting.html
>>
>> Please add (binding) if your vote is binding.
>>
>> Thanks,
>> Thomas
>>
>>
>

[VOTE] Apache Apex Malhar Release 3.2.0-incubating (RC2)

[Thomas Weise]

Hi,

Please vote on the following Apache Apex Malhar 3.2.0-incubating release
candidate. This is the first release of the Malhar library in ASF and it is
based on Apex core 3.2.0-incubating. This is a source release.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 14 binding votes from the PPMC (including 3
votes from IPMC members).

PPMC vote call:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDMWgzncdN7-nxXksE3F2p3xLfCu%2B_nNL-q6p-H_kwASdA%40mail.gmail.com%3E

PPMC vote result:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDPnu2vJZyt%3D9JNmt3nG_nHYk%2B3AseE__SN%3DKXmJ5AskeQ%40mail.gmail.com%3E

List of all issues fixed: http://s.apache.org/2fZ

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1003/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
 (commit:
ff0b0d080ebd8d00cee47321df90dad9357bbead)

PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org

Please try the release and vote; vote will close after 72 hours.

[ ] +1 approve
[ ] -1 disapprove (and reason why)

http://www.apache.org/foundation/voting.html

Please add (binding) if your vote is binding.

Thanks,
Thomas

Re: Access to Wiki

[Thomas Weise]

Thanks!

On Tue, Nov 3, 2015 at 6:37 AM, sebb <seb...@gmail.com> wrote:

> Done
>
> On 3 November 2015 at 06:26, Thomas Weise <t...@apache.org> wrote:
> > I would like to update the status report for the Apex project.
> >
> > Can you please give access to the following user:  ThomasWeise
> >
> > Thanks!
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Access to Wiki

[Thomas Weise]

I would like to update the status report for the Apex project.

Can you please give access to the following user:  ThomasWeise

Thanks!

[ANNOUNCE] Apache Apex Core 3.2.0-incubating released

[Thomas Weise]

The Apache Apex community is pleased to announce release 3.2.0-incubating
(Apex Core). This is the first release since incubation on 2015-08-17.

Changes:
https://github.com/apache/incubator-apex-core/blob/v3.2.0-incubating/CHANGELOG.md

Apache Apex is an enterprise grade native YARN big data-in-motion platform
that unifies stream processing as well as batch processing. Apex was built
for scalability and low-latency processing, high availability and
operability.

Apache Apex is Java based and strives to ease application development on a
platform that takes care of aspects such as stateful fault tolerance,
partitioning, processing guarantees, buffering and synchronization,
auto-scaling etc. Apex comes with Malhar, a rich library of pre-built
operators, including adapters that integrate with existing technologies as
sources and destinations, like message buses, databases, files or social
media feeds.

The source release can be found at:

http://www.apache.org/dyn/closer.lua/incubator/apex/v3.2.0-incubating/apex-3.2.0-incubating-source-release.tar.gz

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at:

http://apex.incubator.apache.org/

Regards,
The Apache Apex community


Disclaimer:
Apache Apex is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Re: [VOTE] Apache Apex Core Release 3.2.0-incubating (RC2)

[Thomas Weise]

The vote passes with 4, +1 binding votes from IPMC members and no -1s:

Chris Nauroth
Justin Mclean
Hitesh Shah
Alan Gates (from PPMC vote thread)

Thanks for voting, we will proceed with the release activities.

Thomas

On Fri, Oct 30, 2015 at 5:47 AM, John D. Ament <johndam...@apache.org>
wrote:

> +1
> On Oct 27, 2015 16:39, "Thomas Weise" <t...@apache.org> wrote:
>
> > Hi,
> >
> > Please vote on the following Apache Apex Core 3.2.0-incubating release
> > candidate. This is the first release after incubation. This is a source
> > release.
> >
> > The Apache Apex PPMC has voted to release this candidate.
> >
> > The community vote passed with 6 binding votes from the PPMC (including 3
> > votes from IPMC members). There were another 9 committer votes in favor
> of
> > the release.
> >
> > PPMC vote call:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDM5wnzmz8CcVbv6d2QM%2BAsaJ6pQ3EyG%2B8XRbSwYkfPX_g%40mail.gmail.com%3E
> >
> > PPMC vote result:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDOY-SpcJfdFiJosoyZ2JidursecietvhT5AgUeX-%3Dw-Tw%40mail.gmail.com%3E
> >
> >
> > List of all issues fixed: http://s.apache.org/SRM
> >
> > Staging directory:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/
> > Source zip:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.zip
> > Source tar.gz:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.tar.gz
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheapex-1001/
> >
> > Git source:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
> >   (commit: d61ca617fd44bf9d74800838341f92018f2c7d10)
> >
> > PGP key:
> > *http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> > <http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org>*
> > KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >
> > More information at:
> > http://apex.incubator.apache.org
> >
> >
> > Please try the release and vote; vote will close after 72 hours.
> >
> > [ ] +1 approve
> > [ ] -1 disapprove (and reason why)
> >
> > http://www.apache.org/foundation/voting.html
> >
> > Please add (binding) if your vote is binding.
> >
> > Thanks,
> > Thomas
> >
>

[RESULT][VOTE] Apache Apex Core Release 3.2.0-incubating (RC2)

[Thomas Weise]

The vote passes with 4, +1 binding votes from IPMC members and no -1s:

Chris Nauroth
Justin Mclean
Hitesh Shah
Alan Gates (from PPMC vote thread)

Thanks for voting, we will proceed with the release activities.

Thomas

On Fri, Oct 30, 2015 at 5:47 AM, John D. Ament <johndam...@apache.org>
wrote:

> +1
> On Oct 27, 2015 16:39, "Thomas Weise" <t...@apache.org> wrote:
>
> > Hi,
> >
> > Please vote on the following Apache Apex Core 3.2.0-incubating release
> > candidate. This is the first release after incubation. This is a source
> > release.
> >
> > The Apache Apex PPMC has voted to release this candidate.
> >
> > The community vote passed with 6 binding votes from the PPMC (including 3
> > votes from IPMC members). There were another 9 committer votes in favor
> of
> > the release.
> >
> > PPMC vote call:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDM5wnzmz8CcVbv6d2QM%2BAsaJ6pQ3EyG%2B8XRbSwYkfPX_g%40mail.gmail.com%3E
> >
> > PPMC vote result:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDOY-SpcJfdFiJosoyZ2JidursecietvhT5AgUeX-%3Dw-Tw%40mail.gmail.com%3E
> >
> >
> > List of all issues fixed: http://s.apache.org/SRM
> >
> > Staging directory:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/
> > Source zip:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.zip
> > Source tar.gz:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.tar.gz
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheapex-1001/
> >
> > Git source:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
> >   (commit: d61ca617fd44bf9d74800838341f92018f2c7d10)
> >
> > PGP key:
> > *http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> > <http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org>*
> > KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >
> > More information at:
> > http://apex.incubator.apache.org
> >
> >
> > Please try the release and vote; vote will close after 72 hours.
> >
> > [ ] +1 approve
> > [ ] -1 disapprove (and reason why)
> >
> > http://www.apache.org/foundation/voting.html
> >
> > Please add (binding) if your vote is binding.
> >
> > Thanks,
> > Thomas
> >
>

[VOTE] Apache Apex Core Release 3.2.0-incubating (RC2)

[Thomas Weise]

Hi,

Please vote on the following Apache Apex Core 3.2.0-incubating release
candidate. This is the first release after incubation. This is a source
release.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 6 binding votes from the PPMC (including 3
votes from IPMC members). There were another 9 committer votes in favor of
the release.

PPMC vote call:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDM5wnzmz8CcVbv6d2QM%2BAsaJ6pQ3EyG%2B8XRbSwYkfPX_g%40mail.gmail.com%3E

PPMC vote result:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDOY-SpcJfdFiJosoyZ2JidursecietvhT5AgUeX-%3Dw-Tw%40mail.gmail.com%3E


List of all issues fixed: http://s.apache.org/SRM

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1001/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
  (commit: d61ca617fd44bf9d74800838341f92018f2c7d10)

PGP key:
*http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
*
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org


Please try the release and vote; vote will close after 72 hours.

[ ] +1 approve
[ ] -1 disapprove (and reason why)

http://www.apache.org/foundation/voting.html

Please add (binding) if your vote is binding.

Thanks,
Thomas