I will take this up.
On Thu, Nov 21, 2019 at 8:05 AM vino yang wrote:
> +1, we can try to use this feature.
>
> Best,
> Vino
>
> Vinoth Chandar 于2019年11月21日周四 上午8:28写道：
>
> > Github actions seems to be able to do this easily as well
> >
> >
>
+1, we can try to use this feature.
Best,
Vino
Vinoth Chandar 于2019年11月21日周四 上午8:28写道：
> Github actions seems to be able to do this easily as well
>
> https://github.com/actions/starter-workflows/blob/master/automation/stale.yml
>
> On Mon, Nov 18, 2019 at 10:33 PM Gurudatt Kulkarni
> wrote:
Github actions seems to be able to do this easily as well
https://github.com/actions/starter-workflows/blob/master/automation/stale.yml
On Mon, Nov 18, 2019 at 10:33 PM Gurudatt Kulkarni
wrote:
> > With templates, we can collect good information while people file the
> > issues..Not sure about
> With templates, we can collect good information while people file the
> issues..Not sure about permissions we have on JIRA to enable bots, but may
> have more luck on github workflows doing these already?
> Can we do templates/required fields with JIRAs as well?
Yes, it is very much possible
Hi Gurudatt and Vinoth,
Thanks for sharing your valuable opinion.
Considering Hudi is still a growing project. I agree that it's better to
keep Github's Issues tab as a way to discuss problems currently.
+1 to introduce issue template and management bot.
Best,
Vino
Vinoth Chandar
Hi Vinoth / Vino,
Just adding my 2 cents to the discussion. Yes, I agree that GitHub issues
are low friction and can be the first line of support. It will help in
keeping the JIRA clean.
Potential solutions that I have come across in the community,
1. Introduce an issue template.
2. Add a bot
@vinoyang. All valid points. I just have 1 argument (all others you are
right and I have always known this tradeoff) for keeping Github issues,
when we are still growing the community and that is : it lets anyone with a
github id raise an issue without forcing to sign up for JIRA account. For
Hi all,
I am not a whimsy, a lot of Apache projects are doing this. Not just Flink,
the project list is very long, including Spark, Kafka, Kylin, Calcite,
Hadoop, storm...
It's no accident that so many projects do this. As the project grows
rapidly, we will find that two ways that report issues
Hi vino,
Thanks for bringing up the discussion.
IMHO, the issues and jira are not opposite and we could use them both for
their advantages. Such as for some simple questions which is no need to
open a jira or send a mail [1], users could get quick response from others
via issues and then close
Hi Vino,
To echo what Nishith was saying, issues is only being used currently for
support i.e looking at stack traces for failures, user errors. Any real
work resulting from that always gets a JIRA.
I mulled the same thing - disabling issues - a while back. The value I see
it adding is
- if you
Hey Vino,
Earlier this year, we actually migrated all issues from GitHub to Jira and
that’s the recommended route to discuss issues (besides the mailing thread) The
remaining issues are either new (folks might open an issue regardless) and we
help navigate those folks to open JIRA’s or there
Hi guys,
Since we use JIRA to manage issues like the other Apache projects. IMHO, we
can stop opening Github's Issues tab [1] to unify issues and reduce
maintenance costs.
This is not the first case, and the Flink community uses this approach.[2]
Of course, if this proposal is adopted, we may
12 matches
Mail list logo
