+1 for me.
mvn clean install passes with Temurin OpenJDK 11.0.16.
Thank you!
Jangho
On 2022-09-06T16:04:08+0900, Byung-Gon Chun wrote:
> +1
>
> Thanks!
> -Gon
>
> On Tue, Sep 6, 2022 at 3:19 PM Jeongyoon Eo wrote:
>
> > +1 for me. Thank you for the effort!
> >
> > I checked:
> >
> > - sha512
+1
I checked RC5 on my Linux box (GNU glibc 2.34 / Linux 5.5.6).
I checked:
- sha512sum matches
- good signature (*.asc) from wy...@apache.org
- `mvn clean install` passes with OpenJDK 11
The build flakiness issue still bothers me, but it seems the test fails only
under limited resources. Let
:04 PM, Byung-Gon Chun wrote:
>>> Hi Jangho,
>>>
>>> Yes. It's the same.
>>>
>>> -Gon
>>>
>>>
>>> On Sun, Feb 23, 2020 at 3:32 PM Jangho Seo wrote:
>>>
>>>> Hi Gon. Thank you for the report.
>>>>
Thank you for your commitership and welcome aboard, Haeyoon!
Thanks,
Jangho Seo
On 2/27/20 7:20 PM, Haeyoon Cho wrote:
> Hi,
>
> Thank you for the warm welcome.
> I am so glad to be a part of the community!
>
> Looking forward to contribute to the project :)
>
> Best,
lies behind the test
failures.
And it's not a compile-time error. Thus the issue Gon encountered while
validating the RC4 should be addressed separately.
Anyway, I'm investigating. Any hands for helping are more than welcome.
Thanks!
Jangho Seo
[1] https://travis-ci.org/apache/incu
Thanks for the info.
Also, Mr. Travis just told me the build is quite flacky. With all the
info, I'll work with WooYeon to solve this problem.
Thanks,
Jangho
On 2/23/20 4:04 PM, Byung-Gon Chun wrote:
> Hi Jangho,
>
> Yes. It's the same.
>
> -Gon
>
>
> On Sun,
106,71]
> incompatible types:
> org.apache.nemo.compiler.frontend.spark.core.rdd.SparkJavaRDD cannot be
> converted to org.apache.nemo.compiler.frontend.spark.core.rdd.JavaRDD
>
> On Sun, Feb 23, 2020 at 12:50 PM Jangho Seo wrote:
>
>> -1
>>
>> Thank you for the work, WooYeon!
>>
>>
-1
Thank you for the work, WooYeon!
Unfortunately, the proposed tarball seems to be in a wrong format. It
has .tar.gz extension, but actually not a gzipped file.
Thanks,
Jangho Seo
On 2/23/20 11:10 AM, John Youngseok Yang wrote:
> +1
>
> Thank you so much for the work WooYeon!
>
&g
+1
I checked RC3 on my Linux box (GNU glibc 2.30 / Linux 5.5.2).
I checked:
- sha512sum matches
- good signature (*.asc) from sa...@apache.org
- `mvn -TC2 clean install` passes with OpenJDK 8 and OpenJDK 11
Thank you,
Jangho
On 2/12/20 7:18 PM, Gyewon Lee wrote:
> +1
>
> Installation successfu
+1
I tested Nemo with Java 8 (OpenJDK 1.8.0_242-b08) on my Linux box (GNU
glibc 2.30 / Linux 5.5.2) successfully.
Thank you,
Jangho
On 2/9/20 5:36 PM, Byung-Gon Chun wrote:
> Nemoers,
>
> Can you check rc2 that Sanha created?
>
> Thanks!
> -Gon
>
>
> On Sat, Feb 8, 2020 at 2:33 PM Jean-Baptiste
Hi Nemoers,
Just a heads up, GSoC organization applications are now open. I think
it's a good time to start thinking about potential topics for Nemo.
The timeline for GSoC 2020 is posted at [1].
Cheers,
Jangho
[1] https://developers.google.com/open-source/gsoc/timeline
I'm happy to report that notifications have been switched to
notifications@nemo.
Cheers,
Jangho
On 12/12/18 5:53 AM, Byung-Gon Chun wrote:
> Jangho,
>
> The list you requested was created.
>
> Cheers,
> Gon
>
> -- Forwarded message -
> From: ASF Self-Service Platform
> Date: Wed,
I reviewed Jira tickets which were our potential topics for GSoC 2018,
and among them supporting Apache Arrow is the sole issue untouched.
We may have to develop more ideas to attract potential GSoC students.
Best,
Jangho
On 12/13/18 2:08 PM, 송원욱 wrote:
> I think it's always great to have new co
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
Yeon Kim wrote:
> 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.
>>
gt; JIRA issue.
>>>> This makes it hard to parse comments only discussed in JIRA.
>>>>
>>>> Maybe we can separate the code-level discussion and high-level design
>>>> discussion.
>>>> For cod-level discussion, we can use GitHub. For hig
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,
ay time)
>
> Once this is merged, I'll send out a vote for the 2nd candidate.
>
> Thanks!
>
> Best,
> Joo Yeon
>
> On Thu, Dec 6, 2018 at 2:10 PM 송원욱 wrote:
>
>> +1 for source-only as well
>> Wonook
>>
>>
>> 2018년 12월 6일 (목) 오후 1:54,
+1 for releasing source-only.
Best,
Jangho
On 12/5/18 6:17 PM, Byung-Gon Chun wrote:
> +1 for releasing only source code
>
> On Wed, Dec 5, 2018 at 6:01 PM Taegeon Um wrote:
>
>> Thanks Joo Yeon!
>>
>>> On 3 Dec 2018, at 6:16 PM, Joo Yeon Kim wrote:
>>>
>>> Thank you mentors for the feedback an
I'm happy to report that tagging issues with right 'fix version' is all
done.
Best,
Jangho
On 11/30/18 3:36 PM, Jangho Seo wrote:
> I'll make sure they're properly handled in no time.
>
> Thanks Joo Yeon for the hard work.
>
> Best,
> Jangho
&g
I'll make sure they're properly handled in no time.
Thanks Joo Yeon for the hard work.
Best,
Jangho
On 11/30/18 3:32 PM, Byung-Gon Chun wrote:
> Thanks a lot, Joo Yeon!
>
>
> On Fri, Nov 30, 2018 at 3:29 PM Joo Yeon Kim wrote:
>
>> Hello Gon,
>>
>> I've been waiting for a few others to mark the
t; Could you open a ticket for disabling notification emails first?
>
> We can talk more about Hudson comments meanwhile.
>
> Best,
> Gon
>
> On Tue, Nov 20, 2018 at 12:37 PM Jangho Seo wrote:
>
>> Thanks for the opinions.
>>
>> +1 for disabling notificatio
Thanks for the opinions.
+1 for disabling notification mails.
Should we open a ticket at INFRA?
Also, I'm okay with disabling Hudson comments at JIRA, although I want
to listen more about it.
Best,
Jangho
On 11/20/18 9:24 AM, Taegeon Um wrote:
> Thanks for the suggestion Max!
>
> +1 for disabli
That also sounds good to me. +1
Best,
Jangho
On 11/15/18 7:29 PM, Byung-Gon Chun wrote:
> Sounds good!
>
> On Thu, Nov 15, 2018 at 6:09 PM Joo Yeon Kim wrote:
>
>> This sounds great to me :) +1
>>
>> On Tue, Nov 13, 2018 at 1:13 PM 송원욱 wrote:
>>
>>> Regarding the discussion, I agree with JB to
Thanks, JB!
Hi Joo Yeon, I think we're ready for staging a release.
Best,
Jangho Seo
On 11/12/18 2:03 PM, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I'm now back from traveling. Please let me know if I can help with the
> release preparation.
>
> Regards
> JB
>
o
properly tag the source tree.
(not scm:git:https://git-wip-us.apache.org/repos/asf/incubator-nemo.git)
Any ideas, Joo Yeon?
Best,
Jangho
On 11/12/18 10:34 AM, Jangho Seo wrote:
> Hi all.
>
> The master build on Linux goes successfully with the following details:
> - Commit hash
Hi all.
We have a pending PR [1] on github.com:apache/incubator-nemo-website
repository.
Wonook, can you handle this PR?
[1] https://github.com/apache/incubator-nemo-website/pull/1
Best,
Jangho
Hi all.
The master build on Linux goes successfully with the following details:
- Commit hash: dbad69d4d
- Kernel version: 4.18.16
- glibc version: 2.28
- JDK: openjdk version "1.8.0_192"
- mvn: Apache Maven 3.6.0
Also, John has kindly confirmed that the master branch builds
successfully on his m
Nemo JIRA issues are now publicly browsable, thanks to the quick
response from INFRA.
On 8/17/18 7:20 PM, Jangho Seo wrote:
> Same here. I can't find an option.
> Considering [1], where ASF INFRA unlocked a JIRA issue type for the
> project, it seems we should ask INFRA for assist
; On Fri, Aug 17, 2018 at 4:57 PM, Byung-Gon Chun wrote:
>
>> Thanks, Jangho.
>>
>> I didn't notice it.
>> I think we should definitely make JIRA issues publicly browsable.
>> I'll check if there's an option we can change. Otherwise, we should file
To Nemo PMC,
Recently I got noticed that Nemo JIRA[1] requires ASF JIRA account for
browsing issues.
That's not the case with with other ASF projects, such as Beam[2],
AVRO[3], etc.
Whether it was intended or not, I think we'd better change this policy,
because I believe publicly accessible issue
Hi Nemo devs,
I just filed a PR to create formatter.xml.
Please check https://github.com/apache/incubator-nemo/pull/106 for the
details.
Comments/patches from Eclipse users (including Arun, of course!) are
more than welcome.
By the way, welcome to the community, Arun!
Regards,
Jangho
On 8/17/1
+1. Thanks.
On 08/08/2018 10:20 AM, Sanha Lee wrote:
> +1. Thanks!
>
> 2018년 8월 8일 (수) 오전 10:14, John Yang 님이 작성:
>
>> +1
>>
>> On Wed, Aug 8, 2018 at 10:03 AM Byung-Gon Chun wrote:
>>
>>> Thanks for volunteering, Joo Yeon!
>>>
>>>
>>> On Wed, Aug 8, 2018 at 9:59 AM, Joo Yeon Kim wrote:
>>>
>>>
Thanks to the INFRA friends, this issue have been resolved.
Regards,
Jangho
On 07/07/2018 09:42 AM, Jangho Seo wrote:
> Here's the ticket: https://issues.apache.org/jira/browse/INFRA-16732
>
> Let's wait for responses from ASF infra.
>
> Regards,
> Jangho
>
>
&
t;
> Thanks.
> -Gon
>
>
> On Sat, Jul 7, 2018 at 9:21 AM, JangHo Seo wrote:
>
>> Hi all,
>>
>> The description of GitHub apache/incubator-nemo repository [1] is
>> "Apache Nemo Incubating https://incubator.apache.org/";.
>> It can be more
Hi all,
The description of GitHub apache/incubator-nemo repository [1] is
"Apache Nemo Incubating https://incubator.apache.org/";.
It can be more descriptive with a right link to the Nemo website.
How about "Apache Nemo (Incubating) - Data Processing System for
Flexible Employment With Different D
Although we already have one "release" in [1], it's just a git tag
without any comments.
If we make a release in this summer, it would be the first time to line
up new features and draft release notes.
For that, Jooyeon has kindly volunteered to be the first release manager.
I created [NEMO-143] R
Hi Jaehyeon,
That sounds great. EditorConfig works with many IDEs and it can assign
different rules for different languages.
Since Nemo is written in multiple languages (Java, Scala, Python, ...),
it will save a lot of time for new contributors.
I'm going to register a JIRA ticket. Thanks!
Jangh
x27;
>
> On the other hand, mechanism-related code should stay in
> 'nemo-runtime-common' and should be exposed only to the
> compiler-backend/nemo.
> Things like 'PhysicalStage' seems to belong to this category, as it'd be
> unlikely that compiler-optimizer
Hi Nemo devs,
Currently Nemo codebase is splitted into multiple Maven modules.
While it's good for ease of maintenance and modularity, a module cannot
reference classes and/or interfaces in other modules unless it declares
them as dependencies in pom.xml.
Sometimes it makes difficult to expose run
scheduling policy, it
> seems that it will resolve my concern.
> Thanks!
>
> Sincerely,
> Sanha
>
> 2018-05-10 15:49 GMT+09:00 JangHo Seo :
>
>> Sorry for the bad formatting. I'm sharing the Google Docs link:
>>
>> https://docs.google.com/document/d/1JoVh
Sorry for the bad formatting. I'm sharing the Google Docs link:
https://docs.google.com/document/d/1JoVh4pvt89fZMHnvJNTgVKEabOzHp8HH0mHJ8rvVBwE/edit?usp=sharing
Regards,
Jangho Seo
On 05/10/2018 03:41 PM, JangHo Seo wrote:
> To Nemo devs,
>
> Our GSoC student Jaehyeon, and two m
d ensured that JaeHyeon has enough access to Nemo
community infra.
(ASF JIRA (username: skystar), Nemo Slack worksapce)
END OF MEETING MINUTES ====
As always, feedbacks welcome.
Regards,
Jangho Seo
To Nemo devs,
I'm happy to say that we have one student participant for GSoC 2018.
Wonook and I will be responsible for mentoring.
The related JIRA ticket is "[NEMO-25] Improve WebUI to use RESTful APIs
by Nemo", which has been a long-awaited issue.
Welcome in JaeHyeon!
Can I ask you to share link
)
> by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
> port 10024)
> with ESMTP id U0kZP3jhj827 for ;
> Tue, 13 Mar 2018 06:59:38 + (UTC)
> Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216])
> by mx1-lw-us.apac
Return-Path:
> Received: (qmail 42439 invoked by uid 99); 13 Mar 2018 06:59:51 -
> Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org)
> (207.244.88.137)
> by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Mar 2018 06:59:51 +
> Received: from [192.168.0.115]
Hi PPMC members,
We're tagging some interesting issues with 'gsoc2018' tag in JIRA.
These issues are currently unassigned and IMHO they require non-trivial
efforts to resolve.
Current issues are:
- NEMO-33: Support Apache Arrow
- NEMO-25: Improve WebUI to use RESTful APIs by Nemo
- NEMO-20: REST
+1 from here, too.
Best,
JangHo Seo
On 03/12/2018 08:30 PM, Woo-Yeon Lee wrote:
> +1
>
> SonarCloud looks interesting!
> I believe our project would be more robust with it :)
>
> Best regards,
> Wooyeon
>
> 2018년 3월 11일 (일) 오후 5:29, Byung-Gon Chun 님이 작성:
>
>
48 matches
Mail list logo
