Google-cloud-go: semver release tags

Created on 5 Apr 2017 · 6Comments · Source: googleapis/google-cloud-go

feature request

Source

adams-sarah

Most helpful comment

Sorta, but not correctly or reliably. I think it's worth having an issue to discuss.

jba on 5 Apr 2017

👍2

All 6 comments

Oops, we already do this.

adams-sarah on 5 Apr 2017

Sorta, but not correctly or reliably. I think it's worth having an issue to discuss.

jba on 5 Apr 2017

👍2

It would also be nice to have some sort of coordinated versioning between google/google-api-go-client and GoogleCloudPlatform/google-cloud-go. Currently it is unclear which versions are compatible (and tested).

fd on 7 Apr 2017

👍1

up for this request. Am using glide and would love semver working properly so I could reliably using the following:

- package: cloud.google.com/go
  version: ~0.7.0

alanma on 18 Apr 2017

We are now tagging with v0.X.0 periodically (approximately weekly). So tools like dep and glide that don't pin to a specific version should get approximately tip. And when they do pin, it will be more granular.

We still aren't using semver fully, which is why our first digit is still zero. We don't distinguish between breaking and non-breaking changes when we tag. Considering that this repo includes packages that range from mature to experimental, it's likely that every week introduces a breaking change.

jba on 22 Jun 2017

Moved to https://github.com/GoogleCloudPlatform/google-cloud-go/wiki/Long-Term-Plans.

jba on 11 Dec 2017

Was this page helpful?

0 / 5 - 0 ratings