adobe / adobe/spectrum-design-data
RFC #735: cross-repo upgrade-timeline automation
- Dominant language
- Rust
- Stars
- 153
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 111
Description
## Context
Open question from RFC #735 (Spec Versioning and Evolution), tracked in `docs/rfc-coordination.md`.
When a breaking spec change ships, platform repos have a two-minor-version migration window. Automate the tracking: tooling or CI that detects when a platform repo's declared `specVersion` is within or outside the migration window, and surfaces a warning or blocks the release accordingly.
## References
- RFC #735: https://github.com/adobe/spectrum-design-data/discussions/735
- `docs/rfc-coordination.md` RFC #735 row
- `spec/evolution.md`
Contributor guide
Research direction
Start by reading docs/rfc-coordination.md and spec/evolution.md, then review RFC #735 for the migration-window rules. Map how platform repositories declare specVersion and how their releases are automated. Done means the cross-repo process detects versions inside or outside the two-minor window and consistently warns or blocks releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100