574370e8d1
BREAKING: Remove Dockerfile.rocm, compose.rocm.yaml, and ROCm image build/push from the release pipeline. Remove AMD quick-start and ROCm references from README and DEVELOPER docs. Update docker-deployment and developer-docs specs to reflect CPU + NVIDIA only. The ROCm variant added significant complexity (4.2GB torch wheel, >20GB container) with limited usage. Users on AMD GPUs should stay on engine v3.2.x or switch to CPU mode. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
821 B
821 B
1. Delete ROCm files
- 1.1 Delete
engine/Dockerfile.rocm - 1.2 Delete
engine/compose.rocm.yaml - 1.3 Delete
assets/directory (ROCm torch wheel)
2. Update release pipeline
- 2.1 Remove ROCm image build, tag, and push from
release-engine.sh - 2.2 Remove ROCm entries from release notes output in
release-engine.sh
3. Update documentation
- 3.1 Remove AMD GPU quick-start section and ROCm references from
README.md - 3.2 Remove ROCm build instructions and
compose.rocm.yamlreferences fromDEVELOPER.md - 3.3 Remove
onnxruntime-rocmmigration note fromDEVELOPER.md
4. Update specs
- 4.1 Update
openspec/specs/docker-deployment/spec.md— remove AMD ROCm requirement, remove ROCm scenarios, update GPU-agnostic requirement to CPU + NVIDIA scope