> Most users just want the latest release. So, if master is equivalent > to the latest tag, then all they ever have to do is "git pull" to get > the latest release. If releases just exist in tags, there is an extra > step to switch to the new tag.
You can check out a specific branch when cloning with the --branch argument: git clone --branch makaanga https://github.com/habari/habari.git (looking up how to spell "makaanga" is certainly an extra step, though (-: ) If users are using git and not release tarballs, I'd expect them to know how to switch branches. My preference is to develop in master and branch/tag for releases (and features). S -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
