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