Official Releases

TODO: It seems like this should just be one part of a larger release procedure.

• All developers involved in the development of C code that uses numpy determine if a different version of numpy should be used to compile the C code. For example, a newer version might be used if it is believed that the newer version fixes bugs that affect surmise or if a newer version is significantly more performant. If a new version is to be used, communicate this and update the version in setup.py and tox.ini.
• Confirm that the numpy values in setup.py and tox.ini are as desired and match. Regenerate and test .c files with Cython via tox. Commit all changes after successful testing.
• As part of PR review, reviewers confirm that all actions including the CI build wheel task are completing successfully.
• A full set of candidate prebuilt binary wheels should be created and manually tested by developers on many different setups and with many different versions of numpy to confirm that they install correctly and pass all tests.
• After publishing the wheels on PyPI, developers shall install surmise directly with pip install on a variety of different machines and with different numpy 183 versions to confirm that installation is successful and all tests are passing.