Thank you for your feedback.
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
It appears that link to an external sources have a separate datatype. Therefore, the migration tool ignores it. I will fix it (see issue [1]).
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?
No, I think my migration config is wrong. I will check it.
We may ignore comments in Jira like 1) author Hudson and text inside "Build success | Build failed" 2) comments from GH bot about a comment to PR.
I added a filter [2]. In the test repository [3] for ARCHETYPE this kind of comments is skipped during the migration.
- Sandra [1] https://github.com/support-and-care/jira-to-gh-issues/issues/10[2] https://github.com/support-and-care/jira-to-gh-issues/blob/d408d661970393f8f6721cf216db0e24ac6cd329/src/main/java/io/pivotal/migration/MArchetpeMigrationConfig.java#L86 [3] https://github.com/support-and-care/mvn-issues-migration-test-archetype/issues?q=is%3Aissue+is%3Aopen+%22ViewProfile.jspa%3Fname%3Dhudson%22
Am 10.01.25 um 23:27 schrieb Sylwester Lachiewicz:
Yes, migration result looks impressive. We may ignore comments in Jira like 1) author Hudson and text inside "Build success | Build failed" 2) comments from GH bot about a comment to PR. Sylwester [image: hudson]Hudson <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hudson> added a comment - 30/Jun/21 17:26 <https://issues.apache.org/jira/browse/MNGSITE-393?focusedCommentId=17372076&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17372076> Build succeeded in Jenkins: Maven » Maven TLP » maven-site » xx-patch-2 #7 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site/job/elharo-patch-2/7/ Edit <https://issues.apache.org/jira/secure/EditComment!default.jspa?id=13290516&commentId=17372076> Delete <https://issues.apache.org/jira/secure/DeleteComment!default.jspa?id=13290516&commentId=17372076> [image: githubbot]ASF GitHub Bot <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=githubbot> added a comment - 23/Apr/23 12:58 <https://issues.apache.org/jira/browse/MNGSITE-393?focusedCommentId=17715440&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17715440> XXX commented on code in PR #212: URL: https://github.com/apache/maven-site/pull/212#discussion_r1174557289 ########## content/apt/guides/mini/guide-http-settings.apt: ########## pt., 10 sty 2025 o 21:51 Hervé Boutemy <herve.bout...@free.fr> napisał(a):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/java/io/pivotal/migration/MArchetpeMigrationConfig.javawow, 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/java/io/pivotal/migration/MCleanMigrationConfig.javaissues 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/java/io/pivotal/migration/MJLinkMigrationConfig.javasame 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
OpenPGP_signature.asc
Description: OpenPGP digital signature
