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 Wang <[email protected]> wrote:

> +1 for moving issues to github due to the bad network.
> Besides we still need handle issues from Jira carefully; indeed active
> community is one of the most important things.
>
> Thanks,
> Xin
>
> 2018-01-04 11:47 GMT+08:00 dongeforever <[email protected]>:
>
> > +1
> >
> > The JIRA system is truly slow in China, which makes it difficult to
> create
> > or update an ISSUE.
> > It would be great to migrate the issues to github.
> >
> >
> > Best Regards
> > dongeforever
> >
> >
> > 2018-01-02 21:24 GMT+08:00 yukon <[email protected]>:
> >
> > > 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 <
> [email protected]>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > > 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.
> > > >
> > > > Other Apache projects do the so it’s certainly possible. I’m not from
> > > > China so forgive my ignorance on this matter but is there a concern
> > that
> > > > GitHub could be possibly blocked? I seem to remember it being blocked
> > > for a
> > > > time in 2016. Using Apache gitbox service [1] may get around that??
> > > >
> > > > Thank,
> > > > Justin
> > > >
> > > > 1.  https://gitbox.apache.org
> > > >
> > > >
> > >
> >
>
>
>
> --
> Thanks,
> Xin
>

Reply via email to