Hi, My 2 cents on this topic; i agree on the current workflow being a bit convoluted. I do see the advantage of having jira since it's more elaborate, but nowadays most important features are also part of Github (releases, issue tracker, fix versions (milestones), roadmap management).
Since the jira version offered by Apache is still the (quite outdated) server version, not the improved cloud version, i would also opt for moving all new issues to Github issues instead of using Jira issues. Jira can then be used as an archive, i see no need for migrating it all. This would reduce the need to switch between both Jira for issues and Github for the PR's. But to be honest, i can live with either solution going forward. Interested to hear other thoughts. Regards, Paul On Wed, Aug 20, 2025 at 3:42 PM Christoph Läubrich <m...@laeubi-soft.de> wrote: > Currently apache-felix is using JIRA for issues, but Github for PRs. > This makes the workflow of contribution a bit harder than needed > (especially as the public signup for this instance is disabled). > > Maven has recently migrated from JIRA to Github for issues[1], so I > wondering if the same should be done for apache-felix as well. Even > though they have migrated all old history form JIRA I think thats not > mandatory if apache-felix for example just would use Github for new and > existing issues. > > This then would make contributions to apache-felix much easier. > > [1] > > https://open-elements.com/posts/2025/08/08/jira-issue-to-github-issue-migration-in-apache-maven/ > -- Paul Rütter | Tech Lead | BlueConic | Wijchenseweg 101, 6538 SW | Nijmegen, The Netherlands | www.blueconic.com
