> I think we should not get rid of JIRA in the short term. > > Since Bigtop is tightly coupled with other Hadoop related projects, > linking JIRA issues between products is important/useful now. > > Projects using Yetus (such as Hadoop and HBase) leverage JIRA > for automatically generating CHANGELOG and RELEASENOTES. > I guess those projects will take time even if they are willing to migrate > from JIRA. > > (Bigtop is using similar way for release notes creation.) > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > > If we accept GitHub issues for contributors without JIRA account, > committers should file a JIRA issue based on the GitHub issue.
I don't agree with this point of view, migration is an inevitable trend. Because Jira is currently riddled with a large number of invalid issues, this has hindered normal use, as evidenced by the Infra crash the other day. To do so Jira is used only for task management, which makes more efficient use of its capabilities. We only need to associate valid Github issues to Jira, and other questions are only used as interaction with the reporter, such as question answering. But we need to find a suitable scheme to deal with the problem of the association between github issue and jira, and this association must be reliable. > Given that the community is not so active recently, > encouraging contributors to request JIRA account creation in mailing lists > should be a viable option. We can't manually maintain the account, because we don't have so much energy, which may make our project worse. To sum up, I think we can migrate from jira to github issue as long as we handle the above issues well. After all, I don't want to experience Apache Infra crash again. ---- Replied Message ---- | From | 李帅<[email protected]> | | Date | 10/25/2022 16:13 | | To | <[email protected]> | | Subject | Re: [DISCUSS] Enable Github Issues for customer-facing questions. | I think we should move all issues to github. it is very convenient to maintain. 吴治国 <[email protected]> 于 2022年10月25日周二 11:40写道： Hello community, Since JIRA is going to disable public signups, we need to spend more time and effort to help create accounts for contributors and users, which makes it harder for users to do bug reports. So I'd like to enable Github Issues for customer-facing questions/bug reports/etc., while maintaining development issues on Jira, just like Infra suggested. Or should we move all our works to Github Issues? But this will affect our old commit messages which contains JIRA number. What's your opinion? Best Regards, Zhiguo Wu
