Target page
reference/changes
Category: verify-then-write
The existing source (github.io reference/migration_guide.rst) only covers
2.0→3.0. The 3.0→4.0 section is completely absent.
What a human must do (~3 hours)
- Review the PandABlocks 4.0 release notes, CHANGELOG, and git log for
breaking changes since 3.0.
- Check the existing
migration_guide.rst (2.0→3.0) for style reference.
- Write a 3.0→4.0 section for
reference/changes covering:
- Config file changes (
boot.txt → config.txt, etc.)
- Wire-protocol breaking changes (if any)
- Removed / renamed blocks or fields
- Build toolchain changes
- Also add a compatibility matrix row for the 3.0→4.0 transition alongside
the existing release_compatibility.rst content.
Post the draft as a comment or PR against the docs branch.
Source
docs/_legacy_rst/ (github.io copies) — reference/migration_guide.rst
(119 words, 2.0→3.0 only)
reference/release_compatibility.rst (32 words)
Target page
reference/changesCategory: verify-then-write
The existing source (
github.io reference/migration_guide.rst) only covers2.0→3.0. The 3.0→4.0 section is completely absent.
What a human must do (~3 hours)
breaking changes since 3.0.
migration_guide.rst(2.0→3.0) for style reference.reference/changescovering:boot.txt→config.txt, etc.)the existing
release_compatibility.rstcontent.Post the draft as a comment or PR against the
docsbranch.Source
docs/_legacy_rst/(github.iocopies) —reference/migration_guide.rst(119 words, 2.0→3.0 only)
reference/release_compatibility.rst(32 words)