Release process for breaking API changes

[gatesn]

Specifically relating to breaks in the Rust API, we'd like to find a better way to release Vortex to allow users to pick up fixes in a timely manner. What this probably looks like is some sort of batching up of breaks into larger releases. I'm not against cutting the 1.0 and leaning into semver here.

I think we should figure out the mechanics of doing this regarding the CI system, release drafter, protected branches, etc etc.

Proposal - 2-track semver model using develop and next branches.

• Protect next in the same way as develop.
• Protect develop with an additional semver check.
• Semver check is run (to print output), but always succeeds when source branch is next
• Release drafter continues to run against develop. We continue to release regularly including bug fixes + patches. Perhaps even automated now?
• Setup workflow to merge develop into next regularly, on every commit probably? Can renovate bot do this as it has auto-approval?
• PRs with breaks target next branch.

[gatesn]

One possible concern I have is if we have multiple concurrent workstreams that each introduce breaking changes. I'd rather we have the option to pick and choose which breaks land in the next release and which ones are deferred.