Update release docs with a section for versioning strategy

[SupunS]

---

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[github-actions]

Cadence Benchstat comparison

This branch with compared with the base branch onflow:master commit 0b1fc2b
The command for i in {1..N}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done was used.
Bench tests were run a total of 7 times on each branch.

Collapsed results for better readability

[turbolent]

Nice! Thank you

[bluesign]

I was just gonna ask something about this: what is the definition of "language-breaking change" ?

[SupunS]

@bluesign

what is the definition of "language-breaking change" ?

A change where an existing Cadence code could be breaking, is considered a language-breaking change. i.e: any backwards incompatible change to the cadence language spec (we don't have the spec documented yet, but in WIP)