[jstanley]

> In short: when a project is being actively developed, tagged releases are the only safe option to ship to users.

If this is such a problem that people need to be warned about it, why not just keep development on branches and make sure master is always stable?

[MartijnBraam]

That wouldn't help because they're not picking master to ship, they're picking mailing list patches and unmerged or rejected Gitlab merge requests directly.

If only they would ship master, that's at least somewhat sane.

[j16sdiz]

The page is missing all these contexts. It don’t make much sense on its own