python-uncompyle6/admin-tools/how-to-make-a-release.md

Table of Contents

• Get latest sources:
• Change version in uncompyle6/version.py
• Update ChangeLog:
• Update NEWS from ChangeLog:
• Make sure pyenv is running and check newer versions
• Switch to python-2.4, sync that up and build that first since it creates a tarball which we don't want.
• Update NEWS from master branch
• Check against all versions
• Make packages and tag
• Upload single package and look at Rst Formating
• Upload rest of versions
• Push tags:

Get latest sources:

git pull

Change version in uncompyle6/version.py:

$ emacs uncompyle6/version.py
$ source uncompyle6/version.py
$ echo $VERSION
$ git commit -m"Get ready for release $VERSION" .

Update ChangeLog:

$ make ChangeLog

Update NEWS.md from ChangeLog:

$ emacs NEWS.md
$ make check
$ git commit --amend .
$ git push   # get CI testing going early

Make sure pyenv is running and check newer versions

$ pyenv local && source admin-tools/check-newer-versions.sh

Switch to python-2.4, sync that up and build that first since it creates a tarball which we don't want.

$ source admin-tools/setup-python-2.4.sh
$ git merge master
# Add and fix merge conflicts
$ git commit

Check against older versions

$ source admin-tools/check-older-versions.sh

Make packages and tag

$ . ./admin-tools/make-dist-older.sh
$ git tag release-python-2.4-$VERSION

$ . ./admin-tools/make-dist-newer.sh
$ git tag release-$VERSION

Upload single package and look at Rst Formating

$ twine upload dist/uncompyle6-${VERSION}-py3.3.egg

Upload rest of versions

$ twine upload dist/uncompyle6-${VERSION}*

Push tags:

$ git push --tags

Check on a VM

$ cd /virtual/vagrant/virtual/vagrant/ubuntu-zesty
$ vagrant up
$ vagrant ssh
$ pyenv local 3.5.2
$ pip install --upgrade uncompyle6
$ exit
$ vagrant halt