mudhorn/prometheus
1
0
Fork 0
mirror of https://github.com/prometheus/prometheus.git synced 2024-11-16 10:34:06 -08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
prometheus/vendor/github.com/uber/jaeger-client-go/RELEASE.md
beorn7 ddefee52dc Update dependencies 
Note that by just running `make update-go-deps`, the K8s Go client was
set to `k8s.io/client-go v11.0.0+incompatible`. However, that doesn't
play well with `k8s.io/apimachinery v0.18.5`. I the manually changed
the Go client line to `k8s.io/client-go v0.18.5`, which made
everything work. I guess Go Modules got confused by the ginormous
v11.0.0 version tag. Or it is a problem that pulling k8s.io/client-go
with git results in a rather old repo without the v0.18.5
tag. github.com/kubernetes/client-go has all the right tags. I
actually don't understand how Go Modules still correctly figures out
the source from the `k8s.io/client-go v0.18.5` line.

If one of the reviewers could enlighten me, I'd much appreciate it.

Signed-off-by: beorn7 <beorn@grafana.com>
2020-07-11 00:42:05 +02:00

644 B
Raw Blame History

Release Process

  1. Create a PR "Preparing for release X.Y.Z" against master branch
    • Alter CHANGELOG.md from <placeholder_version> (unreleased) to <X.Y.Z> (YYYY-MM-DD)
    • Use git log --pretty=format:'- %s -- %an' as the basis for for changelog entries
    • Update JaegerClientVersion in constants.go to Go-X.Y.Z
  2. Create a release "Release X.Y.Z" on Github
    • Create Tag vX.Y.Z
    • Copy CHANGELOG.md into the release notes
  3. Create a PR "Back to development" against master branch
    • Add <next_version> (unreleased) to CHANGELOG.md
    • Update JaegerClientVersion in constants.go to Go-<next_version>dev