Re: [VOTE] Graduate Apache Nemo

+1 Best regards, Joo Yeon 2022년 11월 4일 (금) 오후 4:34, Taegeon Um 님이 작성: > +1 > > Cheers, > Taegeon > > 2022년 11월 4일 (금) 오후 3:55, Woo-Yeon Lee 님이 작성: > > > +1 > > > > Thanks, > > Wooyeon > > > > On Wed, Nov 2, 2022 at 3:09 PM Won Wook SONG wrote: > > > > > With positive discussion[1] > > >

Re: [DISCUSS] Project graduation?

Hello everyone. I also agree that the PMC chair should go to Wonook :) Thank you all for the work and participation to lead this project to graduation! Best regards, Joo Yeon 2022년 11월 1일 (화) 오후 2:06, Byung-Gon Chun 님이 작성: > Hi Won Wook, > > As far as I remember, PPMC members automatically

Re: [#release0.2] Version 0.3 Tag Created in JIRA

reduce the work of release managers > > in the future, and release will be more accelerated. > > It would be nice for former release managers including me and Sanha to > > build a guide together based on experience :) > > > > Thanks, > > Woo-Yeon > >

[#release0.2] Version 0.3 Tag Created in JIRA

Hello Woo-Yeon, Thank you for volunteering! I have created version 0.3 as a release under below link: https://issues.apache.org/jira/projects/NEMO?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=unreleased Please move the remaining issues from 0.2 to 0.3 before the release.

Re: Release v0.2 Feature List

Hello all. @Sanha Let me know when you're ready, I'll hand over the release related material and give you a brief explanation. Thanks a lot for volunteering :) Excited about this second release! Best, Joo Yeon 2019년 9월 19일 (목) 오전 10:02, Byung-Gon Chun 님이 작성: > Wonook, any update? > Sanha, if

Release 0.1 (automatically in progress)

Hi all. I have uploaded our release to: https://dist.apache.org/repos/dist/release/incubator/nemo/0.1-incubating/ The source release should automatically be synced to the mirrors soon. I also have released our maven artifacts here:

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

ts. I > > also tested 'mvn clean install'. > > > > Best regards, > > Hyunsik Choi > > On Mon, Dec 10, 2018 at 7:44 PM Joo Yeon Kim wrote: > > > > > > Hello Nemo PPMC, > > > > > > This is a call for the vote to approve the release, 0.1, re

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

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

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

de > > > > > > 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 feedb

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

Thank you mentors for the feedback and the vote! I've received a few requests to include the features merged to master after rc1, if possible. It looks like I'll be setting up another tarball as per Gon's request anyway, so let's go ahead with another release candidate. Apologies to Davor,

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

g/confluence/display/TAVERNADEV/2016-03+Details%3A+How+to+Review+a+Release > > Thanks. > -Gon > > > On Sun, Dec 2, 2018 at 12:11 PM Joo Yeon Kim wrote: > > > Hello Nemo PPMC, > > > > It is time for us to make the very first release! > > This is a cal

[VOTE] Release Apache Nemo (Incubating) 0.1

Hello Nemo PPMC, It is time for us to make the very first release! This is a call for the vote to approve the release, 0.1.0. Please refer to the information below to vote on this release, and vote: [ ] +1 Release this package as Apache Nemo (incubating) 0.1.0 [ ] 0 I don't feel strongly about

Re: Clean up before the release vote

my issues in accordance with John's > guide. > > > > Best regards, > > Sanha > > > > 2018년 11월 26일 (월) 오전 10:01, Taegeon Um 님이 작성: > > > > > Thanks Joo Yeon! > > > I’ve updated the issues I’ve reported. > > > > > > Best, >

Re: Clean up before the release vote

t; -Gon > > On Fri, Nov 23, 2018 at 3:31 PM Joo Yeon Kim wrote: > > > Thanks for the quick response John. > > > > Since this is the very first release, I'll see how things go. > > I'm also investigating the new power in Nemo JIRA, trying to see if there > >

Re: Clean up before the release vote

Thanks for the quick response John. Since this is the very first release, I'll see how things go. I'm also investigating the new power in Nemo JIRA, trying to see if there is an automatic assignment to fields (ex. automatically setting fix version to 0.2 when creating issues after the first

Clean up before the release vote

Hi all. I've gained administrative access to ASF JIRA Nemo page, and created versions 0.1 and 0.2. Could each of the developers please mark your issues with appropriate fix versions and please let me know on the mailing list when done? Issues resolved before Nov.20 should be v0.1 and those

Re: Version creation in JIRA

I'm guessing no one has the access rights to create a version from the silence...? I'll go ahead and create an INFRA ticket. Best, Joo Yeon On Tue, Nov 20, 2018 at 4:54 PM Joo Yeon Kim wrote: > Hi all. > > I don't seem to be able to locate a menu to create versions in ASF JIRA. >

Re: GitHub notifications

Thanks Jangho for the quick action! I agree with Taegeon about the separate usage of GitHub and JIRA comments. Best, Joo Yeon On Tue, Nov 20, 2018 at 4:28 PM Taegeon Um wrote: > Thanks Jangho! > > I agree that we can archive the PR comments in JIRA, but I think attaching > the PR link to the

Version creation in JIRA

Hi all. I don't seem to be able to locate a menu to create versions in ASF JIRA. Is any one of you able to create a version? If so, where can I find this menu? I was wondering if only the IPMC has the access rights for this option. Please help! :) Thanks in advance, Joo Yeon

Re: First release finally coming soon :)

gt; > not pass without that piece. > > > > Davor > > > > [1] https://beam.apache.org/contribute/release-guide/ > > > > On Sun, Nov 18, 2018 at 6:27 AM Joo Yeon Kim wrote: > > > > > Hi all. > > > > > > I've uploaded a staging arti

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

This sounds great to me :) +1 On Tue, Nov 13, 2018 at 1:13 PM 송원욱 wrote: > Regarding the discussion, I agree with JB to keep the runner in the Nemo > codebase for now, as there are a number of ongoing developments related to > supporting the streaming functionalities. Also, as Nemo relies on >

Re: First release finally coming soon :)

r 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: Apach

Re: First release finally coming soon :)

n Mon, Nov 5, 2018 at 12:37 PM John Yang wrote: > > > Sounds awesome. Thanks Joo Yeon and Jangho! > > > > John > > > > On Mon, Nov 5, 2018 at 9:54 AM Joo Yeon Kim wrote: > > > > > Hi all, > > > > > > Just a littl

Re: First release finally coming soon :)

at 8:29 PM Joo Yeon Kim wrote: > > > Hi all. > > > > Thanks to all of you, Nemo seems to be almost ready for the first > release! > > > > I've checked all the license, notice files and a few other tasks that > need > > to be done. > > >

First release finally coming soon :)

Hi all. Thanks to all of you, Nemo seems to be almost ready for the first release! I've checked all the license, notice files and a few other tasks that need to be done. However, there is one very final task remaining, to get Nemo setup in the Nexus repository. This is to publish maven

Re: Our first release is still in progress!

gt; >> > > > > >> Thanks, > > > > >> John > > > > >> > > > > >> > > > > >> On Wed, Sep 19, 2018 at 5:25 PM John Yang > > > wrote: > > > > >> > > > > >>> Hi Joo Yeon,

Our first release is still in progress!

Hi all. I just wanted to give everyone a heads up regarding the first release. All of the target features have been implemented! Thanks to all who worked hard to get this done :) But it turns out that we want to clear out the copyright issues before the first release (from the offline meeting

How are we doing?

Hello all. It's the end of August and I wanted to check on how we all are doing regarding the first release. Could each person in charge update us about the progress of the responsible items? Anything we need to know besides what we can see on github and JIRA? Best, Joo Yeon

Re: Checkpoint

t take into account > of > > submitting multiple plans and caching, > > so I think I'll need to revise the original design considering current PR > > for caching. > > > > Best regards, > > Jeongyoon > > > > 2018년 8월 20일 (월) 오후 6:55, Joo Yeon Ki

Checkpoint

Hi all, I think it's about time we updated each other with the status/progress/issues if any. Other than the PRs we can see, how is everyone doing with the items to be included for this release? Cheers, Joo Yeon

Re: Release v0.1 Timeline

s 2-3 weeks to get quite right. Of course, mentors are > here to cut the time as much as possible, so do reach out if mentors can be > of any assistance. > > On Tue, Aug 14, 2018 at 1:28 PM, Joo Yeon Kim wrote: > > > Thank you Gon for the great suggestion! > > > > F

Re: Release v0.1 Timeline

. > > Thanks! > -Gon > > On Tue, Aug 14, 2018 at 10:46 AM, Joo Yeon Kim wrote: > > > Hi all. > > > > Here is a list of features we need to complete before the code freeze > > target date, Aug 21st. > > > > 1. Speculative execution using task cloning:

Release v0.1 Timeline

Hi all. Here is a list of features we need to complete before the code freeze target date, Aug 21st. 1. Speculative execution using task cloning: John (Aug. 21) https://issues.apache.org/jira/browse/NEMO-131 2. Support for RDD.cache(): Sanha (Aug. 16)

Release v0.1 Feature List

Hi all. I would like to start a list of features that we are currently working on, and wish to be included in the first release. The below 4 items provide a starting point: 1. Speculative execution using task cloning 2. Support for RDD.cache() 3. Support for Spark ALS 4. Generalized dynamic

Release Management

Hi all, I would like to step up to be the first release manager, if no one else volunteers. Best, Joo Yeon

Build failure on Windows 10

Hi all, I recently cloned our repo on a Windows 10 machine and it looks like the maven build doesn't work. The error occurs when running the integration tests, while trying to open a file to write the outputs at the sink. After a bit of debugging, I found out that the issue is related to Beam

Re: JIRA labels

Labeling issues using either labels or components sounds good to me! If we plan to use the code components as labels @bgchun suggested, let's use JIRA components. But if we plan to add other labels that are not code components in the future (ex. for beginners, bug fix, refactor), let's use