3.1 patch (post 3.1.0)Joe Betz @jpbetz
3.2 patch (post 3.2.0)Joe Betz @jpbetz
3.3 patch (post 3.3.0)Gyuho Lee @gyuho



export VERSION=v2.3.0
export PREV_VERSION=v2.2.5

所有发行版本号都遵循 2.0.0语义版本的格式。


  • 确保GitHub上的相关里程碑已完成。所有相关的问题均应关闭,或移至其他位置。
  • 如有必要,请从 里程碑删除此发行版本。
  • 确保最新的升级文档可用。
  • 如有必要,点击 仓库中最小集群版本的硬编码
  • 如有必要,为新版本添加功能映射。


  • 为了向后兼容,开发者提交针对发行分支提交。提交不应包括合并提交。提交应仅限于错误修复和安全补丁。
  • 可提交的分支应当针对适当的发行分支(base:release-<major>-<minor>). hack/patch/ 可用于自动生成可合并的提交.
  • 发行补丁程序管理器检查提交的拉取请求。请仔细讨论将什么反向移植到该修补程序版本中。每个补丁程序发行版都应严格比其先前版本更好。
  • 发行补丁程序管理器将从最旧的提交开始将这些提交挑选到稳定的分支中。

Write release note

  • Write introduction for the new release. For example, what major bug we fix, what new features we introduce or what performance improvement we make.
  • Put [GH XXXX] at the head of change line to reference Pull Request that introduces the change. Moreover, add a link on it to jump to the Pull Request.
  • Find PRs with release-note label and explain them in NEWS file, as a straightforward summary of changes for end-users.

Tag version

  • Bump hardcoded Version in the repository to the latest version ${VERSION}.
  • Ensure all tests on CI system are passed.
  • Manually check etcd is buildable in Linux, Darwin and Windows.
  • Manually check upgrade etcd cluster of previous minor version works well.
  • Manually check new features work well.
  • Add a signed tag through git tag -s ${VERSION}.
  • Sanity check tag correctness through git show tags/$VERSION.
  • Push the tag to GitHub through git push origin tags/$VERSION. This assumes origin corresponds to “".

Build release binaries and images

  • Ensure docker is available.

Run release script in root directory: ./scripts/ ${VERSION}

It generates all release binaries and images under directory ./release.

Sign binaries, images, and source code

etcd project key must be used to sign the generated binaries and images.$SUBKEYID is the key ID of etcd project Yubikey. Connect the key and run gpg2 --card-status to get the ID.

The following commands are used for public release sign:

cd release
for i in etcd-*{.zip,.tar.gz}; do gpg2 --default-key $SUBKEYID --armor --output ${i}.asc --detach-sign ${i}; done
for i in etcd-*{.zip,.tar.gz}; do gpg2 --verify ${i}.asc ${i}; done

# sign zipped source code files
gpg2 --armor --default-key $SUBKEYID --output ${VERSION}.zip.asc --detach-sign ${VERSION}.zip
gpg2 --verify ${VERSION}.zip.asc ${VERSION}.zip

gpg2 --armor --default-key $SUBKEYID --output ${VERSION}.tar.gz.asc --detach-sign ${VERSION}.tar.gz
gpg2 --verify ${VERSION}.tar.gz.asc ${VERSION}.tar.gz

The public key for GPG signing can be found at CoreOS Application Signing Key

Publish release page in GitHub

  • Set release title as the version name.
  • Follow the format of previous release pages.
  • Attach the generated binaries and signatures.
  • Select whether it is a pre-release.
  • Publish the release!

Publish docker image in

  • Push docker image:
gcloud docker -- login -u _json_key -p "$(cat /etc/gcp-key-etcd.json)"

for TARGET_ARCH in "-arm64" "-ppc64le" ""; do
  gcloud docker -- push${VERSION}${TARGET_ARCH}
  • Add latest tag to the new image on if this is a stable release.

Publish docker image in

  • Build docker images with
for TARGET_ARCH in "amd64" "arm64" "ppc64le"; do GOARCH=${TARGET_ARCH} \
    BINARYDIR=release/etcd-${VERSION}-linux-${TARGET_ARCH} \
    BUILDDIR=release \
    ./scripts/build-docker ${VERSION}
  • Push docker image:
docker login

for TARGET_ARCH in "-arm64" "-ppc64le" ""; do
  docker push${VERSION}${TARGET_ARCH}
  • Add latest tag to the new image on if this is a stable release.

Announce to the etcd-dev Googlegroup

  • Follow the format of previous release emails.
  • Make sure to include a list of authors that contributed since the previous release - something like the following might be handy:
git log ...${PREV_VERSION} --pretty=format:"%an" | sort | uniq | tr '\n' ',' | sed -e 's#,#, #g' -e 's#, $##'

Post release