adobe / adobe/spectrum-design-data
RFC #715: cross-repo product manifest shape and upgrade timeline
- Dominant language
- Rust
- Stars
- 153
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 111
Description
## Context
Open question from RFC #715 (Distributed Design Data Architecture), tracked in `docs/rfc-coordination.md`.
The single-dataset type-compat was resolved by SPEC-032 / PR #914. What remains is the cross-repo shape: how a product manifest references multiple foundation repos, what the upgrade timeline looks like when a foundation version bumps, and any tooling needed to automate compatibility checks across repos.
## References
- RFC #715: https://github.com/adobe/spectrum-design-data/discussions/715
- `docs/rfc-coordination.md` RFC #715 row
- Phase 5 epic: #731
Contributor guide
Research direction
Start with the RFC #715 row in docs/rfc-coordination.md, then read the RFC #715 discussion and SPEC-032/PR #914 for the resolved single-dataset context. This issue is done when the cross-repo manifest shape, foundation upgrade timeline, and compatibility-check tooling scope are agreed and recorded, with alignment to Phase 5 epic #731.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100