Skip to content

RELEASE.md

Latest commit

 

History

History
58 lines (48 loc) · 1.76 KB

RELEASE.md

File metadata and controls

58 lines (48 loc) · 1.76 KB

Update Version Numbers

Update exatomic/_version.py, js/package.jsonandmeta.yaml` version numbers.

Commit and Push Changes

Push changes to your repository (fork).

git add -A
git commit -m "message"
git push

Make a pull request (PR). Once accepted the organization will be tag a new release.

git tag -a X.X.X -m "message"
git push --tags

Remove existing builds (if present)

rm -r dist/*

Release on PyPI

Publish to TestPyPI_ (~/.pypirc required). This requires wheel and twine to be installed.

python setup.py sdist    #python setup.py bdist_wheel
twine upload dist/*

The variable which refers to the alias for the testing or production repository listed in ~/.pypirc.

Release on NPM

Publish the JavaScript extensions on NPM (if required). In the JavaScript directory execute the following commands.

npm whoami   # Confirm correct user if incorrect change with npm adduser, npm login
npm publish

Release on Anaconda

Publish to the exa-analytics_ channel on Anaconda Cloud. This requires that the package hase been released on PyPI. This requires the anaconda package conda-build and anaconda-client (run anaconda login). It is convenient to use a .condarc file to add the conda-forge and exaanalytics channels since some auxiliary packages come from there. Note that to test a build, set uploading to false (anaconda_upload: false in .condarc) and in the meta.yaml source change the url to git_url: ./.

conda build .    # conda build . --output to see location
# For other python version, conda build --python x.x
conda convert -f --platform all /path/to/conda-bld/pltfrm/exa-...tar.bz2 -o /path/to/outputdir/
anaconda upload /path/to/build/build.tar.bz2    # For each build