This page describes the release cadence and process for Thanos project.
We use Semantic Versioning.
NOTE: As Semantic Versioning states all 0.y.z releases can contain breaking changes in API (flags, grpc API, any backward compatibility)
We aim for regular and strict one release per 6 weeks. 6 weeks is counter from first release candidate to another. This means that there is no code freeze or anything like that. We plan to stick to the exact 6 weeks, so there is no rush into being within release (except bug fixes).
No feature should block release.
Additionally, we (obviously) aim for main
branch being stable.
We are assigning a release shepherd for each minor release.
Release shepherd responsibilities:
Release | Time of first RC | Shepherd (GitHub handle) |
---|---|---|
v0.25.0 | (planned) 2021.11.26 | No one ATM |
v0.24.0 | (planned) 2021.10.14 | No one ATM |
v0.23.0 | 2021.09.02 | @bwplotka |
v0.22.0 | 2021.07.06 | @GiedriusS |
v0.21.0 | 2021.05.28 | @metalmatze and @onprem |
v0.20.0 | 2021.04.23 | @kakkoyun |
v0.19.0 | 2021.03.02 | @bwplotka |
v0.18.0 | 2021.01.06 | @squat |
v0.17.0 | 2020.11.18 | @metalmatze |
v0.16.0 | 2020.10.26 | @bwplotka |
v0.15.0 | 2020.08.12 | @kakkoyun |
v0.14.0 | 2020.07.10 | @kakkoyun |
v0.13.0 | 2020.05.13 | @bwplotka |
v0.12.0 | 2020.04.15 | @squat |
v0.11.0 | 2020.02.19 | @metalmatze |
v0.10.0 | 2020.01.08 | @GiedriusS |
v0.9.0 | 2019.11.26 | @bwplotka |
v0.8.0 | 2019.10.09 | @bwplotka |
v0.7.0 | 2019.08.28 | @domgreen |
v0.6.0 | 2019.07.12 | @GiedriusS |
v0.5.0 | 2019.06.31 | @bwplotka |
Process of releasing a minor Thanos version:
v<major>.<minor+1>.0-rc.0
v<major>.<minor>.0
v<major>.<minor>.0-rc.++
Go to step 2.release-xxx
branch and migrate fixes to main.Release is happening on separate release-<major>.<minor>
branch.
Prepare PR to branch release-<major>.<minor>
that will start minor release branch and prepare changes to cut release.
Push the created branch to origin (Thanos repository) to be able to make your PR with the CHANGELOG.md changes against this branch later.
$ git push origin release-<major>.<minor>
For release candidate just reuse same branch and rebase it on every candidate until the actual release happens.
Create small PR to main
(!) to cut CHANGELOG. This helps to maintain new changelog on main.
VERSION
file to version one minor version higher than the released one and dev
suffix. This allows CI to build thanos binary with the version indicating potential next minor release, showing that someone uses non-released binary (which is fine, just better to know this!).Feel free to mimic following PR: https://github.com/thanos-io/thanos/pull/3861
Note that CHANGELOG.md
should only document changes relevant to users of Thanos, including external API changes, performance improvements, and new features. Do not document changes of internal interfaces, code refactorings and clean-ups, changes to the build process, etc. People interested in these are asked to refer to the git history. Format is described in CHANGELOG.md
.
The whole release from release candidate rc.0
to actual release should have exactly the same section. We don’t separate what have changed between release candidates.
Double check backward compatibility:
v1+.y.z
, double check if none of the changes break API compatibility. This should be done in PR review process, but double check is good to have.v0.y.z
, document all incompatibilities in changelog.Double check metric changes:
thanos-mixin
is part of the repository nowUpdate website’s hugo.yaml to have correct links for new release ( add 0.y.z: "/:sections/:filename.md"
).
Update tutorials:
After review, merge the PR and immediately after this tag a version:
tag=$(cat VERSION)
git tag -s "v${tag}" -m "v${tag}"
git push origin "v${tag}"
Signing a tag with a GPG key is appreciated, but in case you can’t add a GPG key to your Github account using the following procedure, you can replace the -s
flag by -a
flag of the git tag
command to only annotate the tag without signing.
Please make sure that you are tagging the merge commit because otherwise GitHub’s UI will show that there were more commits after your release.
Once a tag is created, the release process through CircleCI will be triggered for this tag.
You must create a Github Release using the UI for this tag, as otherwise CircleCI will not be able to upload tarballs for this tag. Also, you must create the Github Release using a Github user that has granted access rights to CircleCI. List of maintainers is available here
Go to the releases page of the project, click on the Draft a new release
button and select the tag you just pushed. Describe release and post relevant entry from changelog. Click Save draft
rather than Publish release
at this time. (This will prevent the release being visible before it has got the binaries attached to it.)
Once tarballs are published on release page, you can click Publish
and release is complete.
Announce #thanos
slack channel.
Pull commits from release branch to main branch for non rc
releases.
After releasing a major version, please cut a release for kube-thanos
as well. https://github.com/thanos-io/kube-thanos/releases Make sure all the flag changes are reflected in the manifests. Otherwise, the process is the same, except we don’t have rc
for the kube-thanos
. We do this to make sure we have compatible manifests for each major versions.
The following changes to the above procedures apply:
-rc.0
to the version (with the corresponding changes to the tag name, the release name etc.).This is a pre-release
box when drafting the release in the Github UI.CHANGELOG.md
, but when you cut the final release later, merge all the changes from the pre-releases into the one final update.Found a typo, inconsistency or missing information in our docs? Help us to improve Thanos documentation by proposing a fix on GitHub here ❤️