update version and release procedure

RELEASE-PROCEDURE.md

@@ -10,6 +10,9 @@ in the source code repo
   `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
@@ -26,8 +29,6 @@ in the source code repo
 
 - upload the resulting files to https://c-ares.org/download/
 
-- update `ares_version.h` for the next version
-
 in the c-ares-www repo
 ----------------------
 

include/ares_version.h

@@ -3,15 +3,15 @@
 #define ARES__VERSION_H
 
 /* This is the global package copyright */
-#define ARES_COPYRIGHT "2004 - 2021 Daniel Stenberg, <daniel@haxx.se>."
+#define ARES_COPYRIGHT "2004 - 2023 Daniel Stenberg, <daniel@haxx.se>."
 
 #define ARES_VERSION_MAJOR 1
 #define ARES_VERSION_MINOR 19
-#define ARES_VERSION_PATCH 0
+#define ARES_VERSION_PATCH 1
 #define ARES_VERSION ((ARES_VERSION_MAJOR<<16)|\
                        (ARES_VERSION_MINOR<<8)|\
                        (ARES_VERSION_PATCH))
-#define ARES_VERSION_STR "1.19.0"
+#define ARES_VERSION_STR "1.19.1"
 
 #if (ARES_VERSION >= 0x010700)
 #  define CARES_HAVE_ARES_LIBRARY_INIT 1