Skip to content

Latest commit

 

History

History
165 lines (118 loc) · 4.91 KB

release_procedure.md

File metadata and controls

165 lines (118 loc) · 4.91 KB
Raw

Release Procedure

This is the procedure to follow to finalize a release of framework-reproducibility (fwr13y). See the official python documentation on setuptools.

1. Merge Release Branch

Thoroughly review the release branch (e.g. r0.4) and merge it into master. Then delete the release branch.

2. Check Version Number

Confirm that __version__ in fwr13y/version.py is correct.

3. Run Tests

Run all the tests and make sure they all pass.

For determinism:

$cd test/d9m
$./all.sh

For seeder: to-be-completed

4. Tag the Release

Tag the state of the repo with the release version (e.g. v0.5.0) in GitHub.

git tag v0.5.0
git push origin v0.5.0

5. Clean the Build Environment

rm -rf build dist *.egg-info

6. Create a Source Distribution

python3 setup.py sdist

This will generate an appropriately-named .tar.gz source distribution file in the dist directory.

After creating the source distribution, check that it contains all the packages, sub-packages, modules, and other files that are expected (and no others). This can be done by viewing the stdout of python3 setup.py sdist, by viewing framework_reproducibility.egg-info/SOURCES.txt, or by running tar -xf on the source distribution file and examing the resuling directory structure.

Note that framework-reproducibility.egg-info/SOURCES.txt is read in (if it exists), modified, and written back out by python3 setup.py sdist. Because of this, if any items are to be excluded from the distribution (e.g. via MANIFEST.in or the packages parameter of setup() in setup.py) then framework-reproducibility.egg-info must be deleted prior to running python3 setup.py sdist, otherwise the exluded items will remain.

Note that to install the source distribution, the user will need to have pip installed, a new-enough version of setuptools and also wheel.

7. Create a Universal Wheel

python3 setup.py bdist_wheel

This will generate an appopriately-named wheel in the dist directory, with a .whl filename extension. Since this is actually a zip file, its contents can be viewed using zipinfo. Use zipinfo to check that all the expected files (and no unexpected files) are present in the wheel.

Note that setup.cfg specifies that wheels are universal by default.

Common Python Packaging Mistakes is a particularly useful resource that I used in preparing the above two steps.

8. Upload to PyPI

Upload the source distribution and the universal wheel to the Python Package Index (PyPI).

The following assumes that $HOME/.pypirc exists and contains the following:

distutils]
index-servers =
    pypi
    testpypi

[pypi]
# Use the upload tool's default repository URL
username: <username>

[testpypi]
repository: https://test.pypi.org/legacy/
username: <username>

8a. Test PyPI Server

twine upload --repository testpypi dist/framework-reproducibility-<version>.tar.gz
twine upload --repository testpypi dist/framework_reproducibility-<version>-py2.py3-none-any.whl

Review the release online (using the link given in the twine output).

Try to install it. As of 2023-02-28, the pip command given on the web page for the package does not work. Instead, use the following pip command.

cd ~/temp
python3 -m venv venv
venv/bin/pip install -i https://test.pypi.org/pypi/ framework-reproducibility
rm -rf venv

A couple of notes related to the PyPI server functionality, as observed from playing with the test server:

  1. You have to upload the source distribution (the .tar.gz file) before the wheel in order for the description to be intepreted as markdown. Presumably, the source format has not been captured in the wheel, at least in the way it's created here, and once it's been set for a given version it cannot be changed.

  2. It can take a few minutes for the versioning seen by pip to be updated. So waiting for a few minutes can resolve issues where it seems that the latest version is not yet available to install, even though you can see it should be availble according to the web page for the distribution. This issue seems to be more common and/or significant on the real/production server. You might also be able to speed things up by using the --no-cache-dir option of pip install.

8b. Real PyPI Server

twine upload --repository pypi dist/framework-reproducibility-<version>.tar.gz
twine upload --repository pypi dist/framework_reproducibility-<version>-py2.py3-none-any.whl

Again, review the release online (using the link given in the twine output) and try to install it, as follows.

cd ~/temp
python3 -m venv venv
venv/bin/pip install framework-reproducibility
rm -rf venv

9. Create the GitHub Release

Finally, on GitHub, create a new release using the version tag created earlier (e.g. v0.4.0).