Migration¶
The migration section explains how legacy names should be retired responsibly instead of merely coexisting forever.
This section is about movement: how readers should adopt canonical package names, what repository consolidation means in practice, how release and validation posture should support the transition, and what evidence is needed before a compatibility package can disappear.
Pages in This Section¶
- Compatibility Overview
- Migration Guidance
- Repository Consolidation
- Canonical Targets
- Dependency Continuity
- Release Policy
- Validation Strategy
- Retirement Conditions
- Retirement Playbook
What This Section Covers¶
- how to move from legacy package names to canonical package names
- how release, dependency, and validation choices support that move
- what a credible retirement path looks like for a compatibility package
Read This Section When¶
- you are planning or reviewing a migration away from legacy package names
- you need the shared rules for compatibility release and retirement decisions
- you want the compatibility layer’s future posture rather than its current catalog entry
Purpose¶
This page provides the route into the compatibility migration guidance.
Stability¶
Keep this page aligned with the migration, validation, and retirement material that the repository currently stands behind.