Suggestion: use 'git flow' and work in another branch, instead of master. Leave master for latest releases. about mysql HOT 4 CLOSED

I agree, I love gitflow. However I do it manually -- I do not use any
tools/plugins. This way I know what I'm actually doing and I don't have to
worry about leaky abstractions :-) It is quite simple. The only thing I've
done is change the repo's default branch to 'develop' which is easy to do
in the repo settings.

from mysql.

The current approach is to leave the "tip" code in master, but use a branch for every release. E.g. the 1.0 line will get a branch where only hotfixes are committed after the release.
Moreover we make use of "Go-tags". The latest compatible release will be tagged with the according Go-version tag, so that go get always loads the latest stable release for this version.

Since now enough people are actively watching this repository, I'd like to try a new Code-Review model to make the master branch more usable. See #60 for details.

from mysql.

I don't know what is "Go-tags" and I would like to. Can you point me to some documentation about this?

from mysql.

http://golang.org/cmd/go/#hdr-Download_and_install_packages_and_dependencies

When checking out or updating a package, get looks for a branch or tag that matches the locally installed version of Go. The most important rule is that if the local installation is running version "go1", get searches for a branch or tag named "go1". If no such version exists it retrieves the most recent version of the package.

from mysql.