Skip to content

Latest commit

 

History

History
31 lines (23 loc) · 1.21 KB

RELEASE.md

File metadata and controls

31 lines (23 loc) · 1.21 KB

How to cut a new stable release

Stable releases are tagged from the uwsgi-2.0 branch. Changes to the uwsgi-2.0 branch are cherry-picked from the master branch.

Before tagging a new release the release notes should be updated and a file named Changelog-2.0.XY.rst where XY is the number of the release created in the uwsgi-docs repository. The newly created changelog file should then be referenced from the index.rst. The release should also be updated in the Download.rst page.

In order to cut a new release you have to first bump the version and then tag with the same version the last commit in git. All the commands are assumed to be run from the uwsgi-2.0 branch.

The the tag should be pushed to git and the source distribution created with the following commands. Please remember to substitute XY with proper version.

git tag 2.0.XY
git push --tags origin HEAD
git archive HEAD --prefix uwsgi-2.0.XY/ -o uwsgi-2.0.XY.tar.gz

Then the tarball must be uploaded to pypi with:

python3 -m twine upload uwsgi-2.0.XY.tar.gz

Once the file is uploaded the Download.rst page of uwsgi-docs repository should be updated.