[asherkin]

Originally Posted by rhelgeby Are you going to switch branching workflow too? Maybe to something like this one: http://nvie.com/posts/a-successful-git-branching-model/ What is the master branch? Does it represent a stable version ready for production at any time, or a development version?

I don't think a convention like this works for projects where the repository isn't usable for end-users out of the box, in a case like SourceMod where it's solely developer oriented, having master be the correct branch for development makes the most sense.

For something like a web application, or even a standalone C++ application, where installing it is equivalent to cloning the repo it makes complete sense to get a production release by default, not so much when you have to also get a mountain of dependencies, compile everything, and then move the binaries elsewhere (and likely to a completely different machine).