tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hyunsik Choi <hyunsik.c...@gmail.com>
Subject Re: [DISCUSSION] 0.12 release
Date Wed, 14 Sep 2016 03:22:29 GMT
If you guys were doing issues scheduled to 0.12, please change fix versions.

Dongjin,
Sure. You can freely change the schedule.

Best regards,
Hyunsik

On Tue, Sep 13, 2016 at 8:21 AM Dongjin Lee <dongjin.lee.kr@gmail.com>
wrote:

> Add to this, it seems like TAJO-1724[^1] and TAJO-1951[^2] was originally
> aimed to be fixed in 0.12.0 but still not on progress. Could you change
> their (expected) fix version to later one? And if there is anyone who is
> working on those issues, I would like to take them.
>
> Regards,
> Dongjin
>
> [^1]: https://issues.apache.org/jira/browse/TAJO-1724
> [^2]: https://issues.apache.org/jira/browse/TAJO-1951
>
> On Tue, Sep 13, 2016 at 10:11 PM, Dongjin Lee <dongjin.lee.kr@gmail.com>
> wrote:
>
> > +1. No Problems.
> >
> > Regards,
> > Dongjin
> >
> > On Tue, Sep 13, 2016 at 8:28 PM, Jihoon Son <jihoonson@apache.org>
> wrote:
> >
> >> +1, I agree with you.
> >>
> >> Best,
> >> Jihoon
> >>
> >> 2016년 9월 13일 (화) 오후 2:02, Jinho Kim <jhkim@apache.org>님이
작성:
> >>
> >> > Hi Hyunsik,
> >> >
> >> > We don’t have blocker issue. So I agree with 0.12 release
> >> > It’s very useful to users, I think.
> >> >
> >> > -Jinho
> >> > Best regards
> >> >
> >> > 2016-09-12 18:14 GMT+09:00 Hyunsik Choi <hyunsik@apache.org>:
> >> >
> >> > > Hi guys,
> >> > >
> >> > > 0.12 release is being delayed because we haven't finish some issues
> >> > > scheduled to 0.12. There are many demands on 0.12 release. The main
> >> > reason
> >> > > is much different code base between master and 0.11.x. Some users
> and
> >> > > developers want to fix bugs in 0.11.x as well as in master branch.
> >> > >
> >> > > I think it's time to release 0.12 release with the current branch
> and
> >> > some
> >> > > critical remain issues.
> >> > >
> >> > > My question is two:
> >> > >  * What do you think about it?
> >> > >  * If we agree with 0.12. release, what issues must be included in
> >> this
> >> > > release?
> >> > >
> >> > > I'm looking forward to your opinions.
> >> > >
> >> > > Best regards,
> >> > > Hyunsik
> >> > >
> >> >
> >>
> >
> >
> >
> > --
> > *Dongjin Lee*
> >
> >
> > *Software developer in Line+.So interested in massive-scale machine
> > learning.facebook: www.facebook.com/dongjin.lee.kr
> > <http://www.facebook.com/dongjin.lee.kr>linkedin:
> > kr.linkedin.com/in/dongjinleekr
> > <http://kr.linkedin.com/in/dongjinleekr>github:
> > <http://goog_969573159>github.com/dongjinleekr
> > <http://github.com/dongjinleekr>twitter: www.twitter.com/dongjinleekr
> > <http://www.twitter.com/dongjinleekr>*
> >
>
>
>
> --
> *Dongjin Lee*
>
>
> *Software developer in Line+.So interested in massive-scale machine
> learning.facebook: www.facebook.com/dongjin.lee.kr
> <http://www.facebook.com/dongjin.lee.kr>linkedin:
> kr.linkedin.com/in/dongjinleekr
> <http://kr.linkedin.com/in/dongjinleekr>github:
> <http://goog_969573159>github.com/dongjinleekr
> <http://github.com/dongjinleekr>twitter: www.twitter.com/dongjinleekr
> <http://www.twitter.com/dongjinleekr>*
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message