> delay a snapshot

The point of a snapshot is that it's a snapshot of current main, bugs and all, even release-blocking bugs.

In my head, the order of stability expectations are (noting that minecraft doesn't do most of these levels, nor do most projects):

1. Long-term support / extended support release

2. Release

3. Release candidate

4. Beta

5. Alpha

6. Snapshot

7. Just-merged master commit

8. Unmerged pull request from a developer on the project

9. Unmerged draft pull request from a developer on the project

10. Unmerged pull request from a stranger

11. .patch file for the source code hosted on pastebin and linked by a total stranger on a cryptocurrency related discord server

12. GitHub's servers

I would expect a fairly major bug to delay a release candidate or beta.

I would expect an absolutely critical bug to prevent merge.

I would not expect any bug which passes the CI tests and gets merged to delay a snapshot, since snapshots are just effectively a scheduled cronjob of "at this date, we cut a release of current main so people can play with it and give feedback if they want without having to figure out how to compile main themselves"