On Sun, Oct 23, 2016 at 07:21:55AM +1000, Stuart Longland wrote: > On Git flow projects, master branch is always the latest stable release.
I'm aware of git-flow, and it sucks. A solution to a problem which for most project won't exist. If you were to do: % git checkout master && git pull Then you'd be running something that was stable, plus code in development for the next release. That's fine. The only criteria for code making it onto master is that it has gone through some testing. If you want to use the latest stable version, you'd checkout that tag: % git checkout -b 2.6.6 something/2.6.6 Beyond that, there's not much more to say about how branching and tagging works. -- Thomas Adam
