Could you tag and/or branch against go release tags? about gocode HOT 4 CLOSED

No, sorry. As README.md says, gocode requires the latest 'release' version of the Go compiler. Having tags is a bad idea, because if Go release doesn't break anything in gocode, no changes are required.

from gocode.

If you can't be bothered to tag your project, it's your project and certainly your choice...but if you think it's a bad idea, that seems like an odd response. Are you sure you understand what it means to tag a project in git?

A git tag isn't a change to your code...it's just a way of marking a historical commit point in your repository. For example, if you've verified that your current code works against 2011-02-01, you could do something like:
git tag compatible-with-go-release.2011-02-01.1

If the Go team releases "release.2011-02-15" next week, and you verify that no changes are necessary in your project, then you merely tag the same point in your repository accordingly:
git tag compatible-with-go-release.2011-02-15

Otherwise, I don't know whether the lack of activity in your project means no changes were necessary, or if it means that you're on vacation or simply haven't noticed that there's been a new Go release.

Not only is this helpful moving forward, but when I need to roll back my go installation to a previous release (which I've occasionally had to do), it's nice to know which version of gocode I should use with it.

(Please consider this request a compliment: I find your tool so incredibly useful that I typically don't update my go installation to the latest release until I verify that gocode has caught up with it!)

from gocode.

Now that there are two reasonable versions of the Go codebase to sync with (weekly and release), will you reconsider?

from gocode.

Yes, I will.

from gocode.