For Developers Only!
This guide is provided for the benefit of the VOC team. As an end user, you shouldn’t ever need to use these instructions.
So, it’s time for a new VOC release! Here’s how to publish a new version so others can benefit from the changes that have been made recently.
Update local checkout
Make sure your developer checkout of VOC is up to date with a:
$ git pull
Confirm that the trunk currently builds for JDK and Android on each version of Python you’re planning to support:
$ ant clean $ ant
Fix any problems that are identified
Make release related changes
- Release history in
- Build number in
- Version number in
Push to Github to get confirmation of a clean CI build.
When CI passes, merge.
Update your checkout of the main
Tag the release. There is a version tag for VOC, plus tags for each of the support libraries that will be released:
$ git tag v0.1.2 $ git tag 3.4-b3 $ git tag 3.5-b3 $ git tag 3.6-b3 $ git push —tags
Build the PyPI packages:
$ python setup.py sdist bdist_wheel
Upload the PyPI packages:
$ twine upload dist/voc-0.1.2*
Check that you have AWS credentials in a file named
.envfile in the root directory of your project checkout:
AWS_ACCESS_KEY_ID=… AWS_SECRET_ACCESS_KEY=… AWS_REGION=us-west-2
Upload the support zipfile to S3:
$ python tools/upload b3
- Check that Read The Docs has updated.