[Poll] Should the default branch be beta or release?

[uvcat7]

We've been having some internal discussion about what the default branch should be.

Currently, it is set to release, so that users who want to compile from source always get a stable version. The problem is it is easy to accidentally fork release or submit a PR to release when developing.

We also have the third option of combining release and beta into main, then tagging release versions with the appropriate commit.

I'm not sure which option is better, but I'd like to do whatever is easiest for the end user.
So, users and developers, which option do you prefer? Feel free to explain your choice.

[convextriangle]

(for posterity) for trunk stuff this seems relevant but others can chime in;
@DolphinChips you mentioned scala and nixos development workflows, can you expand a bit on these options?

[DolphinChips]

can you expand a bit on these options?

in short:

• beta is default
• release-1.x is created for every MINOR release we cut
• v1.x.y tags are created from release-1.x branches
• patches merged to beta get backported to release-1.x branches as needed

[uvcat7]

Sounds like the release crowd has it.