-
Notifications
You must be signed in to change notification settings - Fork 33
Include metafacture-fix #577
Copy link
Copy link
Closed
Description
Merge metafacture-fix repository to ease maintenance and support burden as well as simplify development and use. See metafacture/metafacture-fix#298 for previous discussion.
Preconditions:
- Await the next fix/core release. Release Metafacture core 6.2.0 #580, Release metafacture-fix 1.2.0 based on core 6.2.0 metafacture-fix#390
- Resolve (i.e., close or merge) open pull requests.
- Freeze any activity in old repository.
Course of action:
- Fetch old repository into temporary branch (without tags,
--no-tags). - Merge temporary branch into integration branch (with history,
--allow-unrelated-histories). - Combine common files (
README.md,build.gradle, etc.), preserve current subprojects (metafix*) and namespace (org.metafacture.metafix). - Integrate into
metafacture-runner. - Verify working state (esp. w.r.t. dependencies) for both old and new subprojects (unit tests, integration tests, distribution; branch:
577-merge-metafacture-fix). - Open pull request to merge. Merge metafacture-fix. #586
Post-migration steps:
- Transfer packages to new repository (apparently, Maven packages are always scoped to a repository which cannot be changed).
- Delete packages in old repository.
- Republish
org.metafacture.metafixpackage versions in new repository.
- Verify working state in downstream projects (preview release:
577-merge-metafacture-fix-rc1-SNAPSHOT).- Limetrans (@blackwinter)
- Metafacture Playground (@dr0i, @TobiasNx)
- lobid-resources (@dr0i)
- oersi (@fsteeg)
- Transfer open issues to new repository (can only be done individually). (@TobiasNx, @blackwinter)
- Clean up labels and ensure matching names.
- Add Metafix label to open issues.
- Update issue references in the code (incl. integration tests). 9ed5d4e
- Update
README.mdand description to point to new repository. metafacture/metafacture-fix@6fa7faa - Update/migrate documentation and wiki content. #673
- Archive old repository.
- After next (combined) release: Update/remove dependencies in downstream projects and workflows.
Cleanup:
- Remove
metafix-runner(already done during merge). - Clean up
.gitignorefile (remove obsolete patterns, structure metafacture-fix patterns). 402ee3c - Update Checkstyle config:
-
Find a way to runThis doesn't seem feasible; it's impossible to determine an integration test's up-to-dateness. Instead, they have been changed to run directly from the distribution instead of via Gradle (2661ab8), which reduces the test runtime by about 40-50 %, GitHub Actions runtime by about 30 %. Another option would be to let them run in parallel; but this would be considerably more complicated.metafixintegration tests only when necessary (would otherwise slow down all workflows, including pull request checks).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Type
Projects
Status
Done