Browse Source

Note that we should regenerate configure before running test/versioning.sh

Sam Lantinga 2 years ago
parent
commit
23be3ccc2f
1 changed files with 6 additions and 6 deletions
  1. 6 6
      docs/release_checklist.md

+ 6 - 6
docs/release_checklist.md

@@ -24,10 +24,10 @@
         * set second number in `DYLIB_CURRENT_VERSION` to 0
         * set `DYLIB_COMPATIBILITY_VERSION` to the same value
 
-* Run test/versioning.sh to verify that everything is consistent
-
 * Regenerate `configure`
 
+* Run test/versioning.sh to verify that everything is consistent
+
 * Do the release
 
 ## New bugfix release
@@ -47,10 +47,10 @@
         * set second number in `DYLIB_CURRENT_VERSION` to *patchlevel*
         * Leave `DYLIB_COMPATIBILITY_VERSION` unchanged
 
-* Run test/versioning.sh to verify that everything is consistent
-
 * Regenerate `configure`
 
+* Run test/versioning.sh to verify that everything is consistent
+
 * Do the release
 
 ## After a feature release
@@ -83,8 +83,8 @@
         * set second number in `DYLIB_CURRENT_VERSION` to 0
         * set `DYLIB_COMPATIBILITY_VERSION` to the same value
 
-* Run test/versioning.sh to verify that everything is consistent
-
 * Regenerate `configure`
 
+* Run test/versioning.sh to verify that everything is consistent
+
 * Do the release