-
-
Notifications
You must be signed in to change notification settings - Fork 0
[campaign #252] STEP 6 — MID-TIER: 20-100 file repos (~15 repos) #276
Copy link
Copy link
Open
Labels
meta:campaignCoordinated multi-repo push with a defined end stateCoordinated multi-repo push with a defined end statemigrationPorting between languages or toolchains (e.g. -> AffineScript)Porting between languages or toolchains (e.g. -> AffineScript)priority:p3Low - nice to haveLow - nice to havescope:estateAffects many or all repos across the estateAffects many or all repos across the estatestatus:blockedCannot proceed until a dependency clearsCannot proceed until a dependency clears
Description
Activity
Metadata
Metadata
Assignees
Labels
meta:campaignCoordinated multi-repo push with a defined end stateCoordinated multi-repo push with a defined end statemigrationPorting between languages or toolchains (e.g. -> AffineScript)Porting between languages or toolchains (e.g. -> AffineScript)priority:p3Low - nice to haveLow - nice to havescope:estateAffects many or all repos across the estateAffects many or all repos across the estatestatus:blockedCannot proceed until a dependency clearsCannot proceed until a dependency clears
Part of #252. Blocked by step 5.
Goal
Port the mid-tier repos: 20-100 ReScript files per repo, ~15 repos in this band.
Strategy
src/parser/,src/codegen/,src/cli/) and land one PR per subsystemowner=hyperpolymath,isFork=false)Why blocked by STEP 5
Mid-tier ports surface more diverse Belt / Js / RescriptCore patterns than tail repos. Resolving those via STEP 4 stdlib fill keeps STEP-6 PRs scoped to file-port mechanics rather than mixed stdlib+port scope.
Acceptance
Sequencing
Blocks: STEP 7 implicitly (large-repo strategy lessons learned in mid-tier inform STEP 7+8 sequencing). STEP 9 still parallel-runnable once host bindings (#245+#246) ship.