1curl 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- update `docs/THANKS` 10 11- make sure all relevant changes are committed on the master branch 12 13- tag the git repo in this style: `git tag -a curl-7_34_0`. -a annotates the 14 tag and we use underscores instead of dots in the version number. Make sure 15 the tag is GPG signed (using -s). 16 17- run "./maketgz 7.34.0" to build the release tarballs. It is important that 18 you run this on a machine with the correct set of autotools etc installed 19 as this is what then will be shipped and used by most users on *nix like 20 systems. 21 22- push the git commits and the new tag 23 24- gpg sign the 4 tarballs as maketgz suggests 25 26- upload the 8 resulting files to the primary download directory 27 28in the curl-www repo 29-------------------- 30 31- edit `Makefile` (version number and date), 32 33- edit `_newslog.html` (announce the new release) and 34 35- edit `_changes.html` (insert changes+bugfixes from RELEASE-NOTES) 36 37- commit all local changes 38 39- tag the repo with the same name as used for the source repo. 40 41- make sure all relevant changes are committed and pushed on the master branch 42 43 (the web site then updates its contents automatically) 44 45on github 46--------- 47 48- edit the newly made release tag so that it is listed as the latest release 49 50inform 51------ 52 53- send an email to curl-users, curl-announce and curl-library. Insert the 54 RELEASE-NOTES into the mail. 55 56celebrate 57--------- 58 59- suitable beverage intake is encouraged for the festivities 60 61curl release scheduling 62======================= 63 64Basics 65------ 66 67We do releases every 8 weeks on Wednesdays. If critical problems arise, we can 68insert releases outside of the schedule or we can move the release date - but 69this is very rare. 70 71Each 8 week release cycle is split in two 4-week periods. 72 73- During the first 4 weeks after a release, we allow new features and changes 74 to curl and libcurl. If we accept any such changes, we bump the minor number 75 used for the next release. 76 77- During the second 4-week period we do not merge any features or changes, we 78 then only focus on fixing bugs and polishing things to make a solid coming 79 release. 80 81Coming dates 82------------ 83 84Based on the description above, here are some planned release dates (at the 85time of this writing): 86 87- March 27, 2019 88- May 22, 2019 89- July 17, 2019 90- September 11, 2019 91- November 6, 2019 92