Should we need to map a priority from JIRA to GitHub issues - it can be useful information.
If so, we can add labels like - https://maven.apache.org/developers/conventions/github.html#Priority On Fri, 10 Jan 2025 at 21:51, Hervé Boutemy <herve.bout...@free.fr> wrote: > > Le mercredi 8 janvier 2025, 18:50:59 CET Sandra Parsick a écrit : > > - ARCHETYPE > > > > Migration result: > > https://github.com/support-and-care/mvn-issues-migration-test-archetype > > Used migration config: > > https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/main/j > > ava/io/pivotal/migration/MArchetpeMigrationConfig.java > > wow, I'm impressed: > issues, past closed and still open: > https://github.com/support-and-care/mvn-issues-migration-test-archetype/issues?q=is%3Aissue+ > past milestones: > https://github.com/support-and-care/mvn-issues-migration-test-archetype/milestones?state=closed > > the only missing aspect I found is when a Jira issue links to a PR, like for > example https://issues.apache.org/jira/browse/ARCHETYPE-690 > the issue in GH does not display it: > https://github.com/support-and-care/mvn-issues-migration-test-archetype/issues/647 > > with that as a reference, I'm much more confident, once this PR link is solved > > > > > - MCLEAN > > > > Migration result: > > https://github.com/support-and-care/mvn-issues-migration-test-mclean > > Used migration config: > > https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/main/j > > ava/io/pivotal/migration/MCleanMigrationConfig.java > > issues migration is like ARCHETYPE > but past milestones have not been imported: > https://github.com/support-and-care/mvn-issues-migration-test-mclean/milestones > > is it intentional? > > > > > - MJLINK > > > > Migration result: > > https://github.com/support-and-care/mvn-issues-migration-test-mjlink > > Used migration config: > > https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/main/j > > ava/io/pivotal/migration/MJLinkMigrationConfig.java > > same result as MCLEAN > > > to me, if we fix missing PR links, and import milestones in MCLEAN and MJLINK > like it has been done for ARCHETYPE, we can envision wide migration after > some time to stress test and learn doing releases > > > for tracking progress, if we can, it would be nice to track in Wiki > https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching > > I'll add columns for tracking data migration, and lines for the few tests > > > And if we could migrate issues for MPOM and MASFRES, it would be nice > > Regards, > > Hervé > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
