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 already have a Github account, you can quickly get help - mailing list is not great for pasting/reading code. It helps with that In other words, it helps keep our JIRAs high quality and low noise. Just adding one more perspective. I am coming from “if its not broken, dont fix it yet” angle. Open to hearing everyones thoughts Thanks Vinoth On Fri, Nov 15, 2019 at 3:54 AM Nishith <n3.nas...@gmail.com> wrote: > 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 are existing ones > with a long chain of discussions which should be ideally closed. > I think we can do one more round of clean up on the issues to see if there > are any non-active tickets. > > -Nishith > > Sent from my iPhone > > > On Nov 15, 2019, at 5:12 PM, vino yang <yanghua1...@gmail.com> wrote: > > > > 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 need to migrate the > existing > > issues on Github to JIRA before we can hide it. > > > > This is just a proposal and I want to hear from the community. > > > > Best, > > Vino > > > > [1]: https://github.com/apache/incubator-hudi/issues > > [2]: https://github.com/apache/flink >
