gopkg.in

[GeertJohan]

Any interest in publishing this package using gopkg.in. This basically means you're doing a compatibility promise and can make incompatible changes (if thats ever required) in a new release (v2).

[GeertJohan]

You could just tag the latest commit as v1.0.0 and push a change to the README advertising the import path gopkg.in/alexjlockwood/gcm.v1.
Or:

• register the github organization go-gcm
• move this repo to the go-gcm organization
• fork go-gcm/gcm back to alexjlockwood/gcm and replace the readme.md text in alexjlockwood/gcm so it states that the project has moved.
• Add v1.0.0 tag in go-gcm/gcm
• Update go-gcm/gcm readme.md to advertise gopkg.in/gcm.v1 (note that you can leave out the organization name here, gopkg.in detects the github.com/go-<name>/<name> repo path.

This way everyone importing alexjlockwood/gcm will stay on the current release, even if one day you decide to make a breaking change on master for v2, because that will be on go-gcm/gcm's master.

[0x7061]

+1