Re: [DistributedLog Proposal] Use Github for issue management

Thanks. will creating the basic labels, and update contribute guide for this. On Tue, Aug 15, 2017 at 2:26 PM, Sijie Guo wrote: > 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

Re: [DistributedLog Proposal] Use Github for issue management

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 wrote: > For bookkeeper we are still in a work in progress phase, maybe we can do > the switch for DL when we will

Re: [DistributedLog Proposal] Use Github for issue management

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

Re: [DistributedLog Proposal] Use Github for issue management

On Fri, Aug 11, 2017 at 10:19 AM, Henry Saputra 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

Re: [DistributedLog Proposal] Use Github for issue management

+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 wrote: > Hi all, > > As part of DistributedLog graduation, DistributedLog git repo is renamed to > 'distributedlog