tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hyunsik Choi <hyun...@apache.org>
Subject Re: [DISCUSSION] 0.12 release
Date Mon, 04 Dec 2017 04:40:56 GMT
I rescheduled in-progress issues which are scheduled at 0.12.0 are not
criticial into 0.13.0. Currently, only TAJO-1925 remains in 0.12.0.

@Jaehwa,
Could you check the last comment in TAJO-1925?

Best regards,
Hyunsik Choi

On Sat, Dec 2, 2017 at 9:42 AM Hyunsik Choi <hyunsik@apache.org> wrote:

> Thank you guys.
>
> I just rescheduled 'OPEN' issues scheduled for 0.12.0 to 0.13.0. If we
> need them for 0.12 or next minor release, we can feel free to reschedule
> them.
>
> I'm going to review in-progress issues for 0.12.0 too. If they are not
> critical, I'll reschedule them to next release. If you have any idea,
> please feel free to give us feedback.
>
> Best regards,
> Hyunsik Choi
>
> On Wed, Nov 29, 2017 at 5:57 AM Jong-young Park <eminency@gmail.com>
> wrote:
>
>> I'm glad to hear that.
>>
>> On Wed, Nov 29, 2017 at 4:28 PM 김 진호 <jinossy@gmail.com> wrote:
>>
>> > Thank you for your efforts
>> >
>> > - Jinho
>> >
>> > > On 27 Nov 2017, at 09:47, Hyunsik Choi <hyunsik@apache.org> wrote:
>> > >
>> > > Hi guys,
>> > >
>> > > I'm going to move forward 0.12 release. I just looked into our
>> progress
>> > > about 0.12 in Jira. 239 issues are already resolved in 0.12, 11 are in
>> > > progress, 58 are scheduled yet are not started. As we discussed
>> early, we
>> > > can reschedule not critical issues to next release.
>> > >
>> > > To prepare 0.12 release, I've just created 'branch-0.12.0' from the
>> > current
>> > > master.
>> > >
>> > > Best regards,
>> > > Hyunsik Choi
>> > >
>> > >> On Tue, Sep 13, 2016 at 8:22 PM Hyunsik Choi <hyunsik.choi@gmail.com
>> >
>> > wrote:
>> > >>
>> > >> 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