Streamlining new releases #67
Description
The current expectation is that main is always ready for release.
It is not reasonable to expect the release manager to scan all pull requests to decide whether they are safe to go in, so it should be fine for any team member to go, at any time, to the current Release PR and click the Squash & Merge button.
However, there may be exceptions to that, and this issue aims to discuss those cases.
For example, what to do when there is a PR that requires some oversight before making a release? Say it depends on other PRs that need to be merged, also, before release.
One mechanism may be to use major as the changeset type. But, that is a fairly crude signal, especially if we don't want to make a major release.
Which other mechanisms can we suggest for signaling "hold off on the release until..."?