Or should we move all our works to Github Issues? But this will affect our old commit messages which contains JIRA number.
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. Given that the community is not so active recently, encouraging contributors to request JIRA account creation in mailing lists should be a viable option. Thanks, Masatake Iwasaki On 2022/10/25 12:39, 吴治国 wrote:
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
