Closed matthewfeickert closed 4 years ago
@matthewfeickert should also make an announcement on Issue #26 when this is done.
@dguest The workflow that I recommend in Option 1 would explicitly be:
First release v0.2.0
$ git checkout master && git pull
$ bump2version minor
$ git push origin master --tags
v0.2.0
) in the "Tag version" box and the "Release title" box (to make it easy unless you really want to get descriptive)Next release v0.2.1
$ git checkout master && git pull
$ bump2version patch
$ git push origin master --tags
v0.2.1
) in the "Tag version" box and the "Release title" box (to make it easy unless you really want to get descriptive)@dguest Now that PR #45 is in, this can move forward.
This is done and pandamomium
v0.2.1
is up on PyPI. Congratulations @dguest! :rocket:
After PR #41 is in then we need to get
pandamonium
tov0.2.1
on PyPI. This is because before control was ceded to @dguest in Issue #26 of the PyPI namespace there already was av0.2.0
release of the previouspandamonium
. It is necessary to get pastv0.2.0
on PyPI so the future releases will properly support both sdists and wheels on PyPI.There are two ways to do this:
The easy way of just using the
bump2version
workflow described in PR #36 to release av0.2.0
to PyPI which will only successfully be able to upload av0.2.0
wheel to PyPI as there was already an sdist at the release version, and then immediately afterwards releasev0.2.1
.Apply the attached patch 0001-Bump-version-0.1.0-0.2.0.patch.txt (that GitHub made me name .txt) with
and then run
bump2version
with non-stagged changesto go from
v0.1.0
tov0.2.1
.I would advocate for option 1 as it is the easiest.