Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-06-01 Thread Matteo Merli
To add more context, this topic was discussed recently at ApacheCon. See this talk https://www.youtube.com/watch?v=yWurOHvm5WM Relevant portion start at 18:00. In short, they are saying that the ASF is trying to leverage Github more and more in the future. Matteo On Thu, Jun 1, 2017 at 4:48 PM

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-06-01 Thread Sijie Guo
I think the biggest advantage is JIRA has very good workflow management. Github issues doesn't have such feature. But projects like docker, k8s are using labels for such management. I think more and more large projects (non ASF) are using Github for both issues, pull requests and code. They might a

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-06-01 Thread Venkateswara Rao Jujjuri
I agree, having one place is more convenient. But what is the feature parity between Jira and Github? Here is what I found by googling. https://confluence.sakaiproject.org/display/PMC/Github+Issues+vs+Jira+pros+and+cons On Thu, Jun 1, 2017 at 2:59 PM, Sijie Guo wrote: > Actually thinking a bit m

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-06-01 Thread Sijie Guo
Actually thinking a bit more, I think there is a bit inconvenient in current approach (JIRA for issue tracking and PR for patches). Each time I went to github for reviewing pull requests. I have to go back to JIRA (by copying the JIRA id and typing the URL) to check the descriptions and discussions

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Sijie Guo
I don't any documents at INFRA to point. I do observe more incubator projects are using Github Issues directly when they transfer to the ASF. I knew some of the projects are switching to use Github issues. For example, Traffic Server switches to Github Issues and makes their JIRA readonly at the be

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Flavio Junqueira
I have seen some large projects relying on Github Issues, Docker being one of them. I have recently been using it in the Pravega project and I do find that it doesn't offer right up front some of the features that jira offers. For example, it doesn't give you the ability of creating a workflow,

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Sijie Guo
I believe all the github activities have been mirrored to the mail lists. So I think it is fine to use Github issues. The question will become - use only one? use both? and how to manage these. - Sijie On Fri, May 26, 2017 at 11:06 PM, Bobby Evans wrote: > Apache does have a requirement that c

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Bobby Evans
Apache does have a requirement that community discussions and especially votes are stored on apache servers.  This is often done by linking different systems together (like pull requests to JIRA) or by having a fire-hose of changes from the external system sent to some apache mailing list that i

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Enrico Olivelli
2017-05-26 16:57 GMT+02:00 Sijie Guo : > Hi all, > > Currently we are using Jira for issue tracking and using Github for > managing pull requests. For a new developer, he has to create two accounts > in order to engage with BookKeeper community. I am thinking - shall we also > move the issue tracki

[DISCUSS] Issue Tracking - Jira or Github Issues

2017-05-26 Thread Sijie Guo
Hi all, Currently we are using Jira for issue tracking and using Github for managing pull requests. For a new developer, he has to create two accounts in order to engage with BookKeeper community. I am thinking - shall we also move the issue tracking to use Github Issues (which I believe Apache In