Stable release branch?

Some of you may have noticed that there is a `release` branch in the repository now. I'm curious if we should start distinguishing main development from ABI-compatible bug fixes, perhaps as a warm-up for practicing more strict SemVer when we reach 1.0. It's another thing to pay attention to when fixing bugs and creating/reviewing PRs, but not bad once you get the hang of it. I think we should eventually do this, but I'm not sure it's worth doing yet. A related discussion is what should be present to release 1.0. So a poll, and solicitation of comments:

:+1: Keep `release` branch, potentially tag minor releases like `v0.9.1`. Update contributing guidelines to recommend starting bug-fix branches from `release` and making pull requests to `release`. We'll merge forward (`release` into `main`) routinely as part of maintainer workflow. New feature branches should still start from `main` and the next feature release will be `v0.10.0` (presumably) tagged on `main`.

:-1: Let's wait (for any number of reasons). It's added complexity and not enough value to justify. Let's keep `main` moving for now and perhaps revisit after future feature releases.