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

This commit is contained in:
Sam Lantinga 2022-09-05 11:25:10 -07:00
parent acf397b4df
commit 23be3ccc2f
1 changed files with 6 additions and 6 deletions

View File

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