Hi, I am glad to share my feeling on JIRA and Github's Issue usage. JIRA is a very good issue tracking system, but it is really slow in China. I have remembered clearly when I came to America last year. As usual, I login in JIRA to handle RocketMQ issues, it behaves tremendously well than I was in China. According to my experience with GitHub's Issue, it has smoothly experience in China and America, but it likely missed the feature I most love in JIRA. That is 'components'. I remembered we have discussed that we want to introduce maintainer role when we in incubator status, that’s the most important tool for this rule. Besides, it has no different comparing JIRA. So, if we could transfer our issue track system to GitHub' Issue, maybe a better effective way for global collaboration.
From this reason, I would like to vote +1 for our issue infra. transfer. Best Regards, Von Gosling > 在 2018年1月2日，19:39，yukon <[email protected]> 写道： > > Hi all, > > Consider that most of users and contributors are from China while the JIRA > system has a slow response for us, so I propose that RocketMQ should migrate > from JIRA to Github issue for working efficiency. > > Furthermore, the Github issue has a better integration with pull requests, > could speed up the merge process. > > Any advice is welcome~ > > Regards, > yukon
