Hacker News Reader

You can have long lived release branches in "trunk-based development"?!?

In that case, I guess I haven't ever seen a branching strategy that wasn't "trunk-based." What would that even be?

Anything involving long-lived feature branches especially ones with multiple collaborators, eg git-flow.

If I understand git-flow correctly, it's a trunk (develop) with a release branch (master).

Guess I should have RTFM.

Well written.

It depends on whether the branch ever merges back to the trunk or not.