RELEASE-NOTES.md
to be accurateconfigure.ac
's CARES_VERSION_INFO
, and CMakeLists.txt
's CARES_LIB_VERSIONINFO
set to the same value to denote the current shared object versioning.include/ares_version.h
and set ARES_VERSION_*
definitions to reflect the current version.vX.Y
, where X
is the Major version number, and Y
is the minor version number. If this branch is not yet created, you may create it off the main
branch like:git checkout -b v1.30 main git push -u origin v1.30
vX.Y.Z
where X
is the Major version number, Y
is the minor version number, and Z
is the release. This tag needs to be created from the release branch, for example:git tag -s v1.30.0 -m 'c-ares release 1.30.0' v1.30 git push origin --tags
make dist
, it is best to check out the specific tag fresh and build from that:git clone --depth 1 --branch v1.30.0 https://github.com/c-ares/c-ares c-ares-1.30.0 && \ cd c-ares-1.30.0 && \ autoreconf -fi && \ ./configure && \ make && \ make dist VERSION=1.30.0
gpg -ab c-ares-1.30.0.tar.gz
RELEASE-NOTES.md
as the body. Upload the generated tarball and signature as an artifact.edit index.t
(version number and date),
edit changelog.t
(add the new release in there)
edit download/index.t
for the new release
commit all local changes
push the git commits and the new tag