Fwd: New mailing list queued for creation: notificati...@nemo.apache.org

2018-12-10 Thread Byung-Gon Chun
I made a request to create notifications@nemo. Please refer to the following. -- Forwarded message - From: ASF Self-Service Platform Date: Tue, Dec 11, 2018 at 4:56 PM Subject: New mailing list queued for creation: notificati...@nemo.apache.org To: , ASF Infrastructure Hi

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Taegeon Um
+1 Build success on Ubuntu 16.04.5 LTS Best, Taegeon > On 11 Dec 2018, at 4:07 PM, Gyewon Lee wrote: > > +1 > > I verified the md5 & sha512 checksums and others. The candidate was > successfully built on my MacBook Pro either (Mac OS Mojave 10.14.1). > > Best, > Gyewon > > 2018년 12월 11일 (화

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Gyewon Lee
+1 I verified the md5 & sha512 checksums and others. The candidate was successfully built on my MacBook Pro either (Mac OS Mojave 10.14.1). Best, Gyewon 2018년 12월 11일 (화) 오후 3:38, Sanha Lee 님이 작성: > +1 > > I verified the checksum, PGP signature, release hash, and tag. > `git diff` shows some di

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Gyewon Lee
+1 I verified the md5 & sha512 checksums and others. The candidate was successfully built on my MacBook Pro either (Mac OS Mojave 10.14.1). Best, Gyewon 2018년 12월 11일 (화) 오후 3:38, Sanha Lee 님이 작성: > +1 > > I verified the checksum, PGP signature, release hash, and tag. > `git diff` shows some di

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Sanha Lee
+1 I verified the checksum, PGP signature, release hash, and tag. `git diff` shows some difference between the release candidate files and the repository files, but it was just about the file access permissions. Also, the candidate was successfully built on my MacBook Pro (High Sierra 10.13.3). B

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Jangho Seo
Sorry, my vote is not a binding one. >From the Incubator guide: > The only time when a PPMC member’s vote is binding is for the addition of new PPMC members and committers. Release votes are only binding to IPMC members. Cheers, Jangho On 12/11/18 2:43 PM, Jangho Seo wrote: > +1 (binding) > > I

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Jangho Seo
+1 (binding) I checked the checksum, signature, and the difference with the tagged source tree and they looks all good to me. The source builds successfully with tests and performs well on YARN cluster of 18 nodes. Again, thanks Joo Yeon for the works. Cheers, Jangho On 12/11/18 1:23 PM, Joo Ye

Re: GitHub notifications

2018-12-10 Thread Jangho Seo
According to the infra team [1], there should be a separate mailing list for notifications. Gon, can you create a new mailing list via selfserve.apache.org? Cheers, Jangho [1] https://issues.apache.org/jira/browse/INFRA-17279 On 11/20/18 7:17 PM, Byung-Gon Chun wrote: > Max, thanks for the info

[GitHub] jeongyooneo closed pull request #166: [NEMO-80] SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder

2018-12-10 Thread GitBox
jeongyooneo closed pull request #166: [NEMO-80] SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder URL: https://github.com/apache/incubator-nemo/pull/166 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Joo Yeon Kim
Hi Jangho, Could you check if it's gzipped once again? Thanks, Joo Yeon On Tue, Dec 11, 2018 at 1:10 PM Jangho Seo wrote: > Hi Joo Yeon. > > I see apache-nemo-0.1-incubating-rc2.tar.gz is not gzipped. > What can we do to continue our release process? > > By the way, thanks for the hard work. >

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Jangho Seo
Hi Joo Yeon. I see apache-nemo-0.1-incubating-rc2.tar.gz is not gzipped. What can we do to continue our release process? By the way, thanks for the hard work. Cheers, Jangho On 12/11/18 12:44 PM, Joo Yeon Kim wrote: > Hello Nemo PPMC, > > This is a call for the vote to approve the release, 0.1,

[VOTE] Release Apache Nemo (Incubating) 0.1-rc2

2018-12-10 Thread Joo Yeon Kim
Hello Nemo PPMC, This is a call for the vote to approve the release, 0.1, release candidate 2. Since release candidate 1, I have: - Excluded examples/beam and examples/spark JARs from the maven artifact being published. - Added a checkstyle for Apache license headers - Removed the platform depende

Re: Sending a pull request to Apache Beam for the Nemo Runner?

2018-12-10 Thread 송원욱
It's been a while, but just to let you know that there's a PR up regarding the issue! Anyone who's interested can take a look at https://github.com/apache/beam/pull/7236. Wonook 2018년 11월 16일 (금) 오후 1:16, Jangho Seo 님이 작성: > That also sounds good to me. +1 > > Best, > Jangho > > On 11/15/18 7:29

[GitHub] taegeonum closed pull request #165: [NEMO-221] Confusing error messages for a failure at the client-side …

2018-12-10 Thread GitBox
taegeonum closed pull request #165: [NEMO-221] Confusing error messages for a failure at the client-side … URL: https://github.com/apache/incubator-nemo/pull/165 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[GitHub] taegeonum commented on issue #165: [NEMO-221] Confusing error messages for a failure at the client-side …

2018-12-10 Thread GitBox
taegeonum commented on issue #165: [NEMO-221] Confusing error messages for a failure at the client-side … URL: https://github.com/apache/incubator-nemo/pull/165#issuecomment-446023531 LGTM. I'm merging it. Thanks @yunseong !

[GitHub] taegeonum closed pull request #165: [NEMO-221] Confusing error messages for a failure at the client-side …

2018-12-10 Thread GitBox
taegeonum closed pull request #165: [NEMO-221] Confusing error messages for a failure at the client-side … URL: https://github.com/apache/incubator-nemo/pull/165 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of