Hi, I'm for #2 - simply add issues to GitHub, disable the creation of new issues in jira. - I know that we have many projects ... but we should do it one by one - if project contains not many open issues we can make it read-only at all
we also need a conventions for GitHub issues like is for Jira - https://maven.apache.org/developers/conventions/jira.html On Fri, 22 Nov 2024 at 12:03, Guillaume Nodet <gno...@apache.org> wrote: > > Following the discussion that happened some time ago about switching to GH > issues... > I think we have several options: > 1/ try to migrate issues and make JIRA read only > 2/ make all our JIRA projects unable to create new issues and new issues > would be raised on GH > 3/ do not change JIRA but slowly switch to GH > > #1 looks not feasible, so I rule it out, unless someone knows about tools, > but I don't really see how we could recreate history... > > #2 would simply require a switch that could be easily requested to INFRA, > but until we have made changes to all projects on github, it could be > problematic as JIRA would be read-only while some projects may not have > issues enabled yet > > The reason for #3 would be to migrate projects not all in one shot. All > projects use the same permission scheme in JIRA. I think changing the > scheme would require JIRA administrator privileges, so I don't think any > PMC member can do that easily. However, I know some projects which have > done such migration and used JIRA and GH in parallel. I.e. the source for > release notes would be switched to GH and issues would be either GH issues > or JIRA issues. This is the least disrupting option. At some point, we > can decide to go to #2. > > Thoughts ? > > -- > ------------------------ > Guillaume Nodet > > > > -- > ------------------------ > Guillaume Nodet -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
