5 \___|\___/|_| \_\_____|
7 curl release procedure - how to do a release
8 ============================================
10 [in the source code repo]
12 - edit RELEASE-NOTES to be accurate
16 - make sure all relevant changes are committed on the master branch
18 - tag the git repo in this style: 'git tag -a curl-7_34_0'. -a annotates the
19 tag and we use underscores instead of dots in the version number.
21 - run "./maketgz 7.34.0" to build the release tarballs. It is important that
22 you run this on a machine with the correct set of autotools etc installed
23 as this is what then will be shipped and used by most users on *nix like
26 - push the git commits and the new tag
28 - gpg sign the 4 tarballs as maketgz suggests
30 - upload the 8 resulting files to the primary download directory
32 [data in the curl-www repo]
34 - edit Makefile (version number and date),
35 _newslog.html (announce the new release) and
36 _changes.html (insert changes+bugfixes from RELEASE-NOTES)
38 - commit all local changes
40 - tag the repo with the same tag as used for the source repo
42 - make sure all relevant changes are committed and pushed on the master branch
44 (the web site then updates its contents automatically)
48 - send an email to curl-users, curl-announce and curl-library. Insert the
49 RELEASE-NOTES into the mail.
53 - suitable beverage intake is encouraged for the festivities