Actually, my impression from other projects is that checking out code from Github (or any other repository) just gives you the bleeding edge. If you don't want this, you should download a packaged and released source or binary version or explicitly check out a release tag. (I don't know if this is different for cryptocurrency projects.) Noobs who do not know what they are doing or how to get a tag instead of the default shouldn't be checking out the code from Github in the first place (instead using source downloads for released versions).phelix wrote:Especially for noobs it can be confusing that github defaults to some bleeding edge version. What about creating a release branch and make that the default branch? We can then tag the release branch with versions.
From a more pragmatic point of view, I just want a branch where development is going on and where I can get patches merged relatively easily and quickly after testing and review by others. (Because it only creates a lot of hassles to have lots of "private" branches with proposed changes and develop all of them in parallel without merging them together.) I also do not want this branch to be just for others to check out and test, with the responsibility to merge later to yet another "main" branch. What goes in there should be considered bleeding-edge but officially merged for inclusion in a future release. Whether the branch is "master", "namecoinq" or "bleeding-edge" and whether or not it is checked out by default, I don't care.