Versioning of Cookbook

[peterabbott]

More a comment than a issue.

When releasing new versions of the cookbook it would be nice if you could provide a mechanism to resolve older cookbook versions.

The release pushed to master today broke all our server provisioning because of the change for the apt-repo and version 13 is not available at the new loation

[peterabbott]

at the very least, creating a branch or tag called v0.2.0 from revision ff06dbd62c7a536c55d04b31cc4e5ff8f137d9e7 would be nice

for example git tag v0.2.0 ff06dbd62c7a536c55d04b31cc4e5ff8f137d9e7 git push --tags

[tpbrown]

D'oh - sorry sir. Will make sure I'm not a dolt going forward.

[peterabbott]

I am working on a change to parameterise the Apt and Yum repo's, will do a PR when ready

[tpbrown]

Curious if you have a preference for tags or branches on this?

Also - I'm thinking perhaps the default should be 'latest', and force people to select a specific version if they wanted. It'd be like a default package install.

Thoughts?

[peterabbott]

I guess the convention would be a tag, then if changes are needed a branch would be created from the tag.

Using latest makes sense, as long as there is a nice way to determine what "latest" is? Perhaps a metafile on the server so you don't have to release new versions of the cookbook

Thanks for getting the versions up on the new repo, hopefully we will be able to upgrade to a newer version soon :)

[tpbrown]

The metafile would be nice, but I'll have to convince the Go team to do that work ;-)

For now I'm experimenting with apt/yum list go-server. I've got that working in the Ansible role now.

I'm going to close this and open an issue to reflect "Install latest version by default".