Versioning process migration: current to future
Open
@thibaudcolas is already working on this.
Since Jul 10, 2026.
- Dominant language
- Python
- Stars
- 36
- Forks
- 39
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 3
Description
Part of #403. Follow-up to #445. We want to move from page-based versioning to block-based.
Tasks:
- Figure out whether / how we want to archive existing versioned content.
- #452
Steps
- Add new "version highlight" blocks/content to existing "Latest" pages, for the last 1-2 releases
- Set up redirects system that sets a version picker to the target version and hides corresponding blocks for new versions.
a. Simpler alternative: redirect all requests for unknown locales to english-latest - Delete/archive existing pages for old versions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.