Proposal: Please tag a new release and start using Semantic Versioning

[KateGo520]

I found that this project already supports Go modules. The latest version v1.1.1 committed on 16 Jul 2018, and if module user run "go get gopkg.in/romanyx/recaptcha.v1", the old version v1.1.1 will be required.

$go get gopkg.in/romanyx/recaptcha.v1
go: downloading gopkg.in/romanyx/recaptcha.v1 v1.1.1
go: gopkg.in/romanyx/recaptcha.v1 upgrade => v1.1.1

So, I propose this project to tag a new release and follow Semantic Versioning. For example, v1.0.1, v2.0.0, v3.1.0-alpha, v3.1.0-beta.2etc, so that other project can use tag in go.mod.

[KateGo520]

@lcd1232 Could you help me review this issue? Thx :p

[lcd1232]

@KateGo520 how can I help you with?

[VadimKulagin]

Hello! I also noticed that in the last tag "v.1.1.2" there is an extra dot after the letter "v" which prevents a simple import of this version.

I solved this problem by importing with commit hash:

go get -v github.com/romanyx/recaptcha@23c4e60ed8eebe1e91393b4ea43d4fe1bf7e1da8

Which created the following line in go.mod:

github.com/romanyx/recaptcha v1.1.2-0.20180831135807-23c4e60ed8ee

But I want the package to have a normal tag.

And I think it's worth updating the package import path to github.com/romanyx/recaptcha instead of gopkg.in/romanyx/recaptcha.v1 in the README.