1c-ares release procedure - how to do a release 2============================================== 3 4in the source code repo 5----------------------- 6 7- edit `RELEASE-NOTES` to be accurate 8 9- edit `Makefile.am`'s `CARES_VERSION_INFO`, and `CMakeLists.txt`'s 10 `CARES_LIB_VERSIONINFO` set to the same value to denote the current shared 11 object versioning. 12 13- make sure all relevant changes are committed on the master branch 14 15- tag the git repo in this style: `git tag -a cares-1_14_0` -a annotates the 16 tag and we use underscores instead of dots in the version number. 17 18- run "./maketgz 1.14.0" to build the release tarball. It is important that 19 you run this on a machine with the correct set of autotools etc installed 20 as this is what then will be shipped and used by most users on *nix like 21 systems. 22 23- push the git commits and the new tag 24 25- gpg sign the tarball 26 27- upload the resulting files to https://c-ares.haxx.se/download/ 28 29- update `ares_version.h` for the next version 30 31in the c-ares-www repo 32---------------------- 33 34- edit `index.t` (version number and date), 35 36- edit `changelog.t` (add the new release in there) 37 38- commit all local changes 39 40- tag the repo with the same tag as used for the source repo 41 42- push the git commits and the new tag 43 44inform 45------ 46 47- send an email to the c-ares mailing list. Insert the RELEASE-NOTES into the 48 mail. 49 50celebrate 51--------- 52 53- suitable beverage intake is encouraged for the festivities 54