Jia, it seems that we all agreed to do this and no complaints. let's close this and move forward.
- Sijie On Fri, Aug 11, 2017 at 12:35 PM, Enrico Olivelli <eolive...@gmail.com> wrote: > For bookkeeper we are still in a work in progress phase, maybe we can do > the switch for DL when we will be more organized in BK. > My feeling is that we are on the good way for BK, we did engaged some new > contributors I think because github is open to everyone nowadays > > My two cents > Enrico > > Il ven 11 ago 2017, 21:32 Sijie Guo <guosi...@gmail.com> ha scritto: > > > On Fri, Aug 11, 2017 at 10:19 AM, Henry Saputra <henry.sapu...@gmail.com > > > > wrote: > > > > > Should use same issue management as BookKeeper. > > > > > > One thing that I miss from JIRA is ability to distinguish Epic, Story, > > and > > > Tasks for issues. > > > > > > > Same feeling here :) > > > > > > > > > > On Thu, Aug 10, 2017 at 12:30 AM Sijie Guo <guosi...@gmail.com> wrote: > > > > > > > +1 personally I had a very good experience on using github issues as > > the > > > > issue tracking. > > > > > > > > - Sijie > > > > > > > > On Tue, Aug 8, 2017 at 5:28 PM, Jia Zhai <zhaiji...@gmail.com> > wrote: > > > > > > > > > Hi all, > > > > > > > > > > As part of DistributedLog graduation, DistributedLog git repo is > > > renamed > > > > to > > > > > 'distributedlog <https://github.com/apache/distributedlog>' and > > moved > > > to > > > > > gitbox, as what BookKeeper did a month ago. > > > > > > > > > > While in BookKeeper user feels more effective and smooth to use > > Github > > > > > issue for issue management, I am proposing to also try > > > DistributedLog's > > > > > issue management in Github issue as BP-9 > > > > > <https://cwiki.apache.org/confluence/display/BOOKKEEPER/ > > > > > BP-9+-+Github+issues+for+Issue+Tracking> > > > > > > > > > > Best Regards. > > > > > -Jia > > > > > > > > > > > > > > > -- > > > -- Enrico Olivelli >
