forked from mirror/client_golang
Cut 1.13.1 release (+ documenting release process).
Signed-off-by: bwplotka <bwplotka@gmail.com>
This commit is contained in:
parent
ddd7f0edcd
commit
078f11f85b
|
@ -1,5 +1,11 @@
|
||||||
## Unreleased
|
## Unreleased
|
||||||
|
|
||||||
|
## 1.13.1 / 2022-11-01
|
||||||
|
|
||||||
|
* [BUGFIX] Fix race condition with Exemplar in Counter. #1146
|
||||||
|
* [BUGFIX] Fix `CumulativeCount` value of `+Inf` bucket created from exemplar. #1148
|
||||||
|
* [BUGFIX] Fix double-counting bug in `promhttp.InstrumentRoundTripperCounter`. #1118
|
||||||
|
|
||||||
## 1.13.0 / 2022-08-05
|
## 1.13.0 / 2022-08-05
|
||||||
|
|
||||||
* [CHANGE] Minimum required Go version is now 1.17 (we also test client_golang against new 1.19 version).
|
* [CHANGE] Minimum required Go version is now 1.17 (we also test client_golang against new 1.19 version).
|
||||||
|
|
19
README.md
19
README.md
|
@ -69,3 +69,22 @@ See the [contributing guidelines](CONTRIBUTING.md) and the
|
||||||
[Community section](http://prometheus.io/community/) of the homepage.
|
[Community section](http://prometheus.io/community/) of the homepage.
|
||||||
|
|
||||||
`clint_golang` community is also present on the CNCF Slack `#prometheus-client_golang`.
|
`clint_golang` community is also present on the CNCF Slack `#prometheus-client_golang`.
|
||||||
|
|
||||||
|
### For Maintainers: Release Process
|
||||||
|
|
||||||
|
To cut minor version:
|
||||||
|
|
||||||
|
1. Create new branch `release-<major>.<minor>` on top of main commit you want to cut version from and push it.
|
||||||
|
2. Create new branch on top of release branch.
|
||||||
|
3. Change `VERSION` file.
|
||||||
|
4. Update `CHANGELOG` (only user-impacting changes to mention).
|
||||||
|
5. Create PR, get it reviewed.
|
||||||
|
6. Once merged, create release for `release-<major>.<minor>` tag on GitHub with `<version> / <date>` title.
|
||||||
|
7. Announce on prometheus-announce mailing list, slack and Twitter.
|
||||||
|
8. Merge release branch back to main using "merge without squashing" approach (!).
|
||||||
|
|
||||||
|
To cut patch version:
|
||||||
|
|
||||||
|
1. Create branch on top of release branch you want to use.
|
||||||
|
2. Cherry-pick fixes from main or add commits to fix critical bugs only for that patch release.
|
||||||
|
3. Follow steps 3-8 as above.
|
||||||
|
|
Loading…
Reference in New Issue