- ARCHETYPEThere is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I don't have time to support it so please someone else to help. If we want to copy release notes please be careful such we have some on GitHub. Next I will do a release so we will see what should be changed.
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.java
- MCLEANIt is more complicated - we have two maintained branches I also will prepare a PR for it.
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.java
- 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.java
I located some new issues:1) In some projects, versions like "waiting-for-feedback" or "next release" are used. Should such versions map to GitHub milestone, or would it be better to map to a label? 2) Maybe, this is not a problem. The label color is not synced with the defined label color in the Github Action (https://github.com/apache/maven-gh-actions-shared/blob/main/.github/labels.js). That it is only an issue if the migration tool creates the label. I understood that the Github Action syncs the labels in all Maven repositories, so this issue can be ignored.
If the results are good enough, I can ask Benjamin for a pairing session making the final migration.
- Sandra Am 08.01.25 um 09:47 schrieb Slawomir Jaranowski:
On Wed, 8 Jan 2025 at 03:36, Hervé Boutemy <herve.bout...@free.fr> wrote:we'll need to clarify what projects are guinea pigs, to stress test the issues history copy and releases/milestones I see 3 cited: - ARCHETYPEThere is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I don't have time to support it so please someone else to help. If we want to copy release notes please be careful such we have some on GitHub. Next I will do a release so we will see what should be changed.- MCLEANIt is more complicated - we have two maintained branches I also will prepare a PR for it.- MJLINK MNGSITE does not have any release, then not really something key IMHO for testing migration I see also MPOM, but it seems it has been decided not to migrate history (notice: I find disturbing not finding any link to Jira from https://maven.apache.org/pom/ index.html[1] : given history has not been migrated, we should probably keep a link visible) Le mardi 7 janvier 2025, 18:08:35 CET Slawomir Jaranowski a écrit :Ok be to on track I was created a wiki site - https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+switching As for our ASF MAven initiatives we use wiki to document progress and so on ... so in this case it should be the same. On Tue, 7 Jan 2025 at 17:41, Sandra Parsick <spars...@web.de.invalid> wrote:No manual work ... I thought about not migrate issues at all for this repo - MNGSITEAh, thanks for clarifying. I misunderstood it.We have voted about switching to GitHub ... https://lists.apache.org/thread/h42ls1ccc1flhk2yrkwc6rz05m8rjq6r I'm not going to do about 100 votes ... for each repositoryI understood that the vote was for general, but about actual doing it should be decided per project. What should the process look like? Just doing?We don't need an infra team to enable GitHUb issues.Sorry, my fault. I described it wrong. I meant, the Apache infra team has to be informed to set the Jira project to read-only. Enabling Github Issue could be done by a Maven committer. Am 07.01.25 um 17:25 schrieb Slawomir Jaranowski:On Tue, 7 Jan 2025 at 16:56, Sandra Parsick <spars...@web.de.invalid> wrote:I created migration configuration for the following projects : - MCLEAN [1] - MJLINK [2] - MNGSITE with a filter, so that only open issues are migrated [3] @Slawomir: I know that you want to migrate the issues of MNGSITE manually. The configuration should demonstrate a possibility to migrate only all open issues, automatically. It is just an offer.No manual work ... I thought about not migrate issues at all for this repo - MNGSITEFrom my perspective, these are the next steps: For each project (currently MCLEAN and MJLINK) it should be started a vote. I can prepare temporary repositories that show the migration result of each project if it helps.We have voted about switching to GitHub ... https://lists.apache.org/thread/h42ls1ccc1flhk2yrkwc6rz05m8rjq6r I'm not going to do about 100 votes ... for each repositoryAfter a successful vote, we can start the final migration. Benjamin Marwell offers to help with the orga stuff (like communication with Apache Infra and enabling GitHub issue in the specific repositories) and the final migration.We don't need an infra team to enable GitHUb issues. !!!!!! - I'm starting to think that statuses about such tasks are missing because of too much communicationMeanwhile, I can prepare further migration configurations. What do you think? - Sandra [1] https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/m ain/java/io/pivotal/migration/MCleanMigrationConfig.java [2] https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/m ain/java/io/pivotal/migration/MJLinkMigrationConfig.java [3] Am 07.01.25 um 12:22 schrieb Sandra Parsick:After a discussion with Gerd Aschemann, I moved the migration list from the Github Issue to the repository of the migration tool [1]. I adjusted the list according to already provided feedback. If someone wants to have write permission to this repository, please let me know it, I will assign it to you (I only need your GitHub nickname). I think that will be easier to maintain the migration list and to change the tool, if necessary. Am 06.01.25 um 15:03 schrieb Sandra Parsick:First we need to enable issues on GitHub to allow migrating issues. So please add a column "GitHub Issues enabled"
OpenPGP_signature.asc
Description: OpenPGP digital signature
