-
Notifications
You must be signed in to change notification settings - Fork 372
Release instructions
Kodi Arfer edited this page Jun 23, 2022
·
21 revisions
- Set the release date in NEWS and merge the pull request for the new release.
- Build and test the PyPI package on your local machine (see https://packaging.python.org/distributing/ for complete instructions).
git clean -dfx
- Make sure the new release is tagged (
git tag x.y.z -m 'Version x.y.z'
) and thatversion.py
is up to date (runpython3 get_version.py
) before making the final distribution package. -
python3 setup.py sdist
to create the source distribution.- We no longer distribute wheels, because this prevents precompiling the Hy code during installation.
- Create a new virtualenv and install the created package there for testing:
virtualenv tenv -p python3 && cd tenv && source ./bin/activate && pip install fastentrypoints && pip install [source distribution file] && deactivate && source ./bin/activate && echo `type hy` && echo '(+ 1 1)' | hy
- Publish the release on GitHub.
git push --tags origin
- Add an item to https://github.com/hylang/hy/releases .
- Fast-forward the
stable
branch on GitHub. - Check that all's well with the documentation: https://readthedocs.org/projects/hy/builds
- Let @paultag and @Kodiologist know that things are ready. Either of them can upload the package into PyPI.
twine upload dist/*
- Similarly, publish the corresponding new release of Hyrule.
- Add a commit (only for the new version tag, not
master
) that sets Hyrule's version number and declares a dependency on the Hy release insetup.py
.
- Add a commit (only for the new version tag, not
- Use the new releases of Hy and Hyrule for the web console.