Skip to content

issue/1373 - reduce InfiniCore to a component manifest - #1405

Closed
voltjia wants to merge 2 commits into
issue/1373from
issue/1373-1
Closed

issue/1373 - reduce InfiniCore to a component manifest#1405
voltjia wants to merge 2 commits into
issue/1373from
issue/1373-1

Conversation

@voltjia

Copy link
Copy Markdown
Collaborator

Summary

  • Reduce InfiniCore to a component manifest containing only .gitmodules, LICENSE, README.md, and the InfiniRT, InfiniOps, and InfiniCCL gitlinks.
  • Pin InfiniRT at 08677bb566ee3009586ae4194e6f7e50a4bbad66, InfiniOps at 296271487beb594a248fd463e5fff14f7ab74293, and InfiniCCL at 1f3e24a68448c3f2af4475d603ed7c2b85e28f12.
  • Remove the legacy runtime, operator, Python package, build system, tests, scripts, and repository workflows from this repository.

Motivation

InfiniCore should coordinate compatible component revisions instead of maintaining duplicate runtime and operator implementations. Keeping a single authoritative implementation in each component removes the legacy API surface and makes the repository boundary explicit.

Repository Surface

The resulting repository has exactly six tracked paths and no build or packaging entry point of its own. README.md documents the manifest role and recursive submodule checkout only.

Validation

  • Verified git ls-files returns exactly the six intended paths.
  • Verified all three component entries use gitlink mode 160000 and resolve to the pinned revisions.
  • Verified git submodule update --init --recursive --depth 1 checks out the complete component graph.
  • Verified neither the final tree nor the PR commit range contains the removed legacy status type.
  • Verified git diff --check origin/issue/1373...HEAD passes.

Closes#1373

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@voltjia