You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by 俊平堵 <ju...@apache.org> on 2020/01/02 04:04:06 UTC
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
The discussion has been for over 1 week and looks like no objection get
raised out.
The consensus has been made - let's move the discussions to JIRA instead of
Github issues.
Thanks,
Junping
俊平堵 <ju...@apache.org> 于2019年12月25日周三 上午11:13写道:
> Hi,
> Continue with TubeMQ's wechat group discussion, shall we use JIRA or
> Github issue to track issues for TubeMQ?
> My recommendation is to use JIRA, for following reasons:
> 1. Most of existing Apache projects use JIRA to track issues which is more
> friendly to project management with lots of functions.
> 2. Github (and issue) is not own by Apache, so it could be more risky to
> lost history or access especially during repository migration, etc.
> 3. Existing workflow of many projects are JIRA based, and many of tubemq
> contributors/committers are from them, such as hadoop, flink, spark, hbase,
> etc. It could be more friendly to early contributor.
> Thoughts?
>
> Thanks,
>
> Junping
>
>