It seems to migration is a main voice from our guys. If no further feedback, I
am glad to put it forward :-)
Best Regards,
Von Gosling
> 在 2018年1月9日,09:20,Roman Shtykh 写道:
>
> +1 for migration. Github seems to suffice for how we handle issues now.
>
> -- Roman
>
+1 for migration. Github seems to suffice for how we handle issues now.
-- Roman
On Tuesday, January 2, 2018, 9:13:53 PM GMT+9, yukon
wrote:
The missed context:
Consider that most of users and contributors are from China while the JIRA
system has a slow response
I am +1 to migration.
Creating a ticket on current JIRA is too slow.
Zhanhui Li
> 在 2018年1月5日,下午10:54,yukon 写道:
>
> Hi all,
>
> Please note that we cannot migrate any existing Jira tickets to Github
> Issues. We need to start fresh and migrate the incomplete tickets to
>
Hi all,
Please note that we cannot migrate any existing Jira tickets to Github
Issues. We need to start fresh and migrate the incomplete tickets to
Github manually.
I will open a migrate ticket to INFRA next week if there is no opposite
voice.
Regards,
yukon
On Fri, Jan 5, 2018 at 5:39 PM, Xin
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
Hi Justin,
RocketMQ is hosted on Gitbox now, and every software engineer has a proper
way to reach GitHub, no need to worry about it :)
Regards,
yukon
On Tue, Jan 2, 2018 at 8:22 PM, Justin Mclean
wrote:
> Hi,
>
> > Consider that most of users and contributors are
Hi Justin,
That makes sense, +dev list.
Please let us know if anyone is in trouble when submitting a report to JIRA
system.
On Tue, Jan 2, 2018 at 7:59 PM, Justin Mclean
wrote:
> Hi,
>
> IMO it would be better to discuss this on dev list as I think as it
> impacts