That should be doable. Worse case scenario is that the committer creates a JIRA and links it to the github issue. And then we do all the discussion on github. The downside is we lost any information on the JIRA side. When it comes to a migration, those links to github issues might be dead. But think it another way: we link PRs instead of patch files nowadays. So I guess the strong dependency to github is somewhat OK.
吴治国 <[email protected]> 於 2022年10月26日 週三 晚上11:48寫道： > Thank you all for participant the discussion. > > > As Masatake said, it's critical to auto generate CHANGELOG and > RELEASENOTES, which is currently done via JIRA. > > Since moving development issues to Github Issues will cause many problems > (not just CHANGELOG and RELEASENOTES), my intention is not to migrate all > issues to Github, only customer-facing questions. > > > Given that the community is not so active recently, encouraging > contributors to request JIRA account creation in mailing lists should be a > viable option. > > As far as I know, most Bigtop users are also developers, which is > different from Ambari, so Masatake's opinion makes sense to me. > > But at the same time, I also know that many people are not used to using > JIRA or Email to ask questions, so I want to enable Github Issues for > Ambari, at least try it once and see how it works, but we can talk more > details on Ambari dev mailing list, where I raised an exact same discussion > thread. > > Best Regards, > Zhiguo Wu > > > 2022年10月26日 10:21，Evans Ye <[email protected]> 写道： > > > > As Masatake said, it's critical to auto generate CHANGELOG and > > RELEASENOTES, which is currently done via JIRA. > > I'm more preferred to Masatake's proposal unless there's a solution to > auto > > gen from github issues. > > > > 李帅 <[email protected]>於 2022年10月25日 週二，下午4:13寫道： > > > >> 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 > >>> > >> > >
