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 2019/12/25 03:13:14 UTC
[DISCUSS] Shall we use JIRA or Github issue to track issues?
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
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by 俊平堵 <ju...@apache.org>.
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
>
>
Re: [DISCUSS] Shall we use JIRA or Github issue to track
issues?(Internet mail)
Posted by lamber liu <la...@gmail.com>.
+1 for JIRA
On Thu, Dec 26, 2019 at 9:59 AM osgooli(李致波) <os...@tencent.com> wrote:
> +1 for JIRA
>
> -----邮件原件-----
> 发件人: 俊平堵 <ju...@apache.org>
> 发送时间: 2019年12月25日 11:13
> 收件人: dev@tubemq.apache.org
> 主题: [DISCUSS] Shall we use JIRA or Github issue to track issues?(Internet
> mail)
>
> 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
>
答复: [DISCUSS] Shall we use JIRA or Github issue to track issues?(Internet mail)
Posted by "osgooli (李致波)" <os...@tencent.com>.
+1 for JIRA
-----邮件原件-----
发件人: 俊平堵 <ju...@apache.org>
发送时间: 2019年12月25日 11:13
收件人: dev@tubemq.apache.org
主题: [DISCUSS] Shall we use JIRA or Github issue to track issues?(Internet mail)
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
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by Guangxu Cheng <gu...@gmail.com>.
+1 for JIRA.
JIRA is more powerful. Beginners may need to sign up for a JIRA account,
but I don't think this is a barrier for developers.
俊平堵 <ju...@apache.org> 于2019年12月26日周四 上午11:59写道：
> Thanks waterlx for comments and raised questions - that's next discussion I
> would like to call.
> Hadoop use a different way - most of discussions are happening on JIRA
> instead of github, but it really depends on how the tubemq community think.
>
> Thanks,
>
> Junping
>
> 李响 <wa...@gmail.com> 于2019年12月26日周四 上午10:45写道：
>
> > +1 for JIRA to track issue.
> > Another topic is how to review and comment code ? HBase currently prefers
> > using JIRA to track issue, putting a link to github on JIRA and reviewing
> > on github. (Please correct me if I am wrong about that) In that way, it
> > seems lead to that we have almost nothing but only a link and the
> original
> > description on JIRA, while storing the most useful parts (review and
> > discussion history) on github.
> >
> > On Thu, Dec 26, 2019 at 10:14 AM Yiheng Wang <yi...@gmail.com> wrote:
> >
> > > +1 for JIRA.
> > >
> > > Github Issue is not as powerful as JIRA.
> > >
> > > On Thu, Dec 26, 2019 at 9:53 AM Kayne Wu <wu...@gmail.com>
> > wrote:
> > >
> > > > +1 for JIRA
> > > > JIRA a more open place, with more developers participating in
> > > development
> > > > and discussions,
> > > > which helps tubemq to develop and growing faster.
> > > >
> > > >
> > > >
> > > > Goson zhang <go...@gmail.com> 于2019年12月26日周四 上午9:38写道：
> > > >
> > > > > +1 for JIRA.
> > > > >
> > > > > tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
> > > > >
> > > > > > +1 for JIRA.
> > > > > >
> > > > > > JIRA provides rich functions for tagging & releasing which, in
> > > GitHub,
> > > > > > should
> > > > > > take more efforts to setup and maintain. Also I second that JIRA
> is
> > > > > hosted
> > > > > > by Apache makes it more reliable for TubeMQ an Apache project.
> > > > > >
> > > > > > As a reminder, if we choose to use JIRA, make sure we close
> GitHub
> > > > issue
> > > > > > entry so that newcomer doesn't get confused.
> > > > > >
> > > > > > Best,
> > > > > > tison.
> > > > > >
> > > > > >
> > > > > > 俊平堵 <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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > 李响 Xiang Li
> >
> > 手机 cellphone ：+86-136-8113-8972
> > 邮件 e-mail ：waterlx@gmail.com
> >
>
--
Best Regards
Guangxu
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by 俊平堵 <ju...@apache.org>.
Thanks waterlx for comments and raised questions - that's next discussion I
would like to call.
Hadoop use a different way - most of discussions are happening on JIRA
instead of github, but it really depends on how the tubemq community think.
Thanks,
Junping
李响 <wa...@gmail.com> 于2019年12月26日周四 上午10:45写道：
> +1 for JIRA to track issue.
> Another topic is how to review and comment code ? HBase currently prefers
> using JIRA to track issue, putting a link to github on JIRA and reviewing
> on github. (Please correct me if I am wrong about that) In that way, it
> seems lead to that we have almost nothing but only a link and the original
> description on JIRA, while storing the most useful parts (review and
> discussion history) on github.
>
> On Thu, Dec 26, 2019 at 10:14 AM Yiheng Wang <yi...@gmail.com> wrote:
>
> > +1 for JIRA.
> >
> > Github Issue is not as powerful as JIRA.
> >
> > On Thu, Dec 26, 2019 at 9:53 AM Kayne Wu <wu...@gmail.com>
> wrote:
> >
> > > +1 for JIRA
> > > JIRA a more open place, with more developers participating in
> > development
> > > and discussions,
> > > which helps tubemq to develop and growing faster.
> > >
> > >
> > >
> > > Goson zhang <go...@gmail.com> 于2019年12月26日周四 上午9:38写道：
> > >
> > > > +1 for JIRA.
> > > >
> > > > tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
> > > >
> > > > > +1 for JIRA.
> > > > >
> > > > > JIRA provides rich functions for tagging & releasing which, in
> > GitHub,
> > > > > should
> > > > > take more efforts to setup and maintain. Also I second that JIRA is
> > > > hosted
> > > > > by Apache makes it more reliable for TubeMQ an Apache project.
> > > > >
> > > > > As a reminder, if we choose to use JIRA, make sure we close GitHub
> > > issue
> > > > > entry so that newcomer doesn't get confused.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > >
> > > > > 俊平堵 <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
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
> --
>
> 李响 Xiang Li
>
> 手机 cellphone ：+86-136-8113-8972
> 邮件 e-mail ：waterlx@gmail.com
>
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by 李响 <wa...@gmail.com>.
+1 for JIRA to track issue.
Another topic is how to review and comment code ? HBase currently prefers
using JIRA to track issue, putting a link to github on JIRA and reviewing
on github. (Please correct me if I am wrong about that) In that way, it
seems lead to that we have almost nothing but only a link and the original
description on JIRA, while storing the most useful parts (review and
discussion history) on github.
On Thu, Dec 26, 2019 at 10:14 AM Yiheng Wang <yi...@gmail.com> wrote:
> +1 for JIRA.
>
> Github Issue is not as powerful as JIRA.
>
> On Thu, Dec 26, 2019 at 9:53 AM Kayne Wu <wu...@gmail.com> wrote:
>
> > +1 for JIRA
> > JIRA a more open place, with more developers participating in
> development
> > and discussions,
> > which helps tubemq to develop and growing faster.
> >
> >
> >
> > Goson zhang <go...@gmail.com> 于2019年12月26日周四 上午9:38写道：
> >
> > > +1 for JIRA.
> > >
> > > tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
> > >
> > > > +1 for JIRA.
> > > >
> > > > JIRA provides rich functions for tagging & releasing which, in
> GitHub,
> > > > should
> > > > take more efforts to setup and maintain. Also I second that JIRA is
> > > hosted
> > > > by Apache makes it more reliable for TubeMQ an Apache project.
> > > >
> > > > As a reminder, if we choose to use JIRA, make sure we close GitHub
> > issue
> > > > entry so that newcomer doesn't get confused.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > >
> > > > 俊平堵 <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
> > > > >
> > > >
> > >
> >
>
--
李响 Xiang Li
手机 cellphone ：+86-136-8113-8972
邮件 e-mail ：waterlx@gmail.com
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by Yiheng Wang <yi...@gmail.com>.
+1 for JIRA.
Github Issue is not as powerful as JIRA.
On Thu, Dec 26, 2019 at 9:53 AM Kayne Wu <wu...@gmail.com> wrote:
> +1 for JIRA
> JIRA a more open place, with more developers participating in development
> and discussions,
> which helps tubemq to develop and growing faster.
>
>
>
> Goson zhang <go...@gmail.com> 于2019年12月26日周四 上午9:38写道：
>
> > +1 for JIRA.
> >
> > tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
> >
> > > +1 for JIRA.
> > >
> > > JIRA provides rich functions for tagging & releasing which, in GitHub,
> > > should
> > > take more efforts to setup and maintain. Also I second that JIRA is
> > hosted
> > > by Apache makes it more reliable for TubeMQ an Apache project.
> > >
> > > As a reminder, if we choose to use JIRA, make sure we close GitHub
> issue
> > > entry so that newcomer doesn't get confused.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > 俊平堵 <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
> > > >
> > >
> >
>
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by Kayne Wu <wu...@gmail.com>.
+1 for JIRA
JIRA a more open place, with more developers participating in development
and discussions,
which helps tubemq to develop and growing faster.
Goson zhang <go...@gmail.com> 于2019年12月26日周四 上午9:38写道：
> +1 for JIRA.
>
> tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
>
> > +1 for JIRA.
> >
> > JIRA provides rich functions for tagging & releasing which, in GitHub,
> > should
> > take more efforts to setup and maintain. Also I second that JIRA is
> hosted
> > by Apache makes it more reliable for TubeMQ an Apache project.
> >
> > As a reminder, if we choose to use JIRA, make sure we close GitHub issue
> > entry so that newcomer doesn't get confused.
> >
> > Best,
> > tison.
> >
> >
> > 俊平堵 <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
> > >
> >
>
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by Goson zhang <go...@gmail.com>.
+1 for JIRA.
tison <wa...@gmail.com> 于2019年12月25日周三 上午11:19写道：
> +1 for JIRA.
>
> JIRA provides rich functions for tagging & releasing which, in GitHub,
> should
> take more efforts to setup and maintain. Also I second that JIRA is hosted
> by Apache makes it more reliable for TubeMQ an Apache project.
>
> As a reminder, if we choose to use JIRA, make sure we close GitHub issue
> entry so that newcomer doesn't get confused.
>
> Best,
> tison.
>
>
> 俊平堵 <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
> >
>
Re: [DISCUSS] Shall we use JIRA or Github issue to track issues?
Posted by tison <wa...@gmail.com>.
+1 for JIRA.
JIRA provides rich functions for tagging & releasing which, in GitHub,
should
take more efforts to setup and maintain. Also I second that JIRA is hosted
by Apache makes it more reliable for TubeMQ an Apache project.
As a reminder, if we choose to use JIRA, make sure we close GitHub issue
entry so that newcomer doesn't get confused.
Best,
tison.
俊平堵 <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
>