RFC #76: Final touches.

Author: zyp

text/0076-amaranth-boards-versioning-policy.md

@@ -1,6 +1,6 @@
-- Start Date: (fill in with date at which the RFC is merged, YYYY-MM-DD)
+- Start Date: (fill in with date at which the RFC is merged, 2025-05-12)
 - RFC PR: [amaranth-lang/rfcs#76](https://github.com/amaranth-lang/rfcs/pull/76)
-- Amaranth Issue: [amaranth-lang/amaranth#0000](https://github.com/amaranth-lang/amaranth/issues/0000)
+- Amaranth Issue: [amaranth-lang/amaranth#1595](https://github.com/amaranth-lang/amaranth/issues/1595)
 
 # `amaranth-boards` versioning policy
 
@@ -21,6 +21,11 @@ Packages with direct (e.g. git) dependencies aren't allowed on PyPI, so by not p
 - Increment `y` and do a new release any time there's been done significant additions.
 - Increment `x`, reset `y` and do a new release any time there are breaking changes.
 
+A breaking change is anything that requires manual intervention for code that previously worked fine.
+I.e. a change to a board file which previously had two pins incorrectly swapped would not be a breaking change; a change to names of resources across multiple boards would be.
+
+This should be implemented by automatically releasing every commit to `main` whose HEAD message doesn't contain `[breaking change]` or `[breaking-change]` with a version like `v0.x.y` where `y` is the number of commits since the last breaking change, and automatically tagging every commit that does with a tag `v0.(x+1).0`.
+
 ## Drawbacks
 [drawbacks]: #drawbacks