diff options
Diffstat (limited to 'doc/HOWTO_RELEASE.rst.txt')
| -rw-r--r-- | doc/HOWTO_RELEASE.rst.txt | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/HOWTO_RELEASE.rst.txt b/doc/HOWTO_RELEASE.rst.txt index 61bf71da0..cde342a74 100644 --- a/doc/HOWTO_RELEASE.rst.txt +++ b/doc/HOWTO_RELEASE.rst.txt @@ -259,15 +259,15 @@ There are three steps to the process. not backward compatible. 2. If the C_API_VERSION in the first step has changed, or if the hash of - the API has changed, the cversions.txt file needs to be updated. To - check the hash, run the script numpy/core/cversions.py and note the api hash - that is printed. If that hash does not match the last hash in cversions.txt - the hash has changed. Using both the appropriate C_API_VERSION and hash, - add a new entry to cversions.txt. If the API version was not changed, but - the hash differs, you will need to comment out the previous entry for that - API version. For instance, in NumPy 1.9 annotations were added, which - changed the hash, but the API was the same as in 1.8. The hash serves as a - check for API changes, but it is not definitive. + the API has changed, the cversions.txt file needs to be updated. To check + the hash, run the script numpy/core/cversions.py and note the api hash that + is printed. If that hash does not match the last hash in cversions.txt the + hash has changed. Using both the appropriate C_API_VERSION and hash, add a + new entry to numpy/core/code_generators/cversions.txt. If the API version + was not changed, but the hash differs, you will need to comment out the + previous entry for that API version. For instance, in NumPy 1.9 annotations + were added, which changed the hash, but the API was the same as in 1.8. The + hash serves as a check for API changes, but it is not definitive. If steps 1 and 2 are done correctly, compiling the release should not give a warning "API mismatch detect at the beginning of the build. |