Skip to content

PYTHON-2434 Automatically combine release wheels + sdist into one archive #803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Nov 24, 2021
Merged

PYTHON-2434 Automatically combine release wheels + sdist into one archive #803

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3983f49
PYTHON-2434 Combine release wheels into one archive
ShaneHarvey Nov 20, 2021
b80e789
PYTHON-2434 add axis for release tag to fix this error:
ShaneHarvey Nov 23, 2021
63befd5
PYTHON-2434 Merge old manylinux files first
ShaneHarvey Nov 23, 2021
dabcd13
PYTHON-2434 Put all release tasks in the same variant
ShaneHarvey Nov 23, 2021
84cef0b
PYTHON-2434 Update release process docs
ShaneHarvey Nov 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
PYTHON-2434 Update release process docs
  • Loading branch information
@ShaneHarvey
ShaneHarvey committed Nov 23, 2021
commit 84cef0b3dc4089f69be9ccee8554907542e13e92
37 changes: 13 additions & 24 deletions RELEASE.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,48 +55,37 @@ Doing a Release
8. Push commit / tag, eg ``git push && git push --tags``.

9. Pushing a tag will trigger a release process in Evergreen which builds
wheels and eggs for manylinux, macOS, and Windows. Wait for these jobs to
complete and then download the "Release files" archive from each task. See:
wheels for manylinux, macOS, and Windows. Wait for the "release-combine"
task to complete and then download the "Release files all" archive. See:
https://evergreen.mongodb.com/waterfall/mongo-python-driver?bv_filter=release

Unpack each downloaded archive so that we can upload the included files. For
the next steps let's assume we unpacked these files into the following paths::
The contents should look like this::

$ ls path/to/manylinux
$ ls path/to/archive
pymongo-<version>-cp310-cp310-macosx_10_9_universal2.whl
...
pymongo-<version>-cp38-cp38-manylinux2014_x86_64.whl
...
$ ls path/to/windows/
pymongo-<version>-cp38-cp38-win_amd64.whl
...

10. Build the source distribution::

$ git clone [email protected]:mongodb/mongo-python-driver.git
$ cd mongo-python-driver
$ git checkout "<release version number>"
$ python3 setup.py sdist

This will create the following distribution::

$ ls dist
pymongo-<version>.tar.gz

11. Upload all the release packages to PyPI with twine::
10. Upload all the release packages to PyPI with twine::

$ python3 -m twine upload dist/*.tar.gz path/to/manylinux/* path/to/mac/* path/to/windows/*
$ python3 -m twine upload path/to/archive/*

12. Make sure the new version appears on https://pymongo.readthedocs.io/. If the
11. Make sure the new version appears on https://pymongo.readthedocs.io/. If the
new version does not show up automatically, trigger a rebuild of "latest":
https://readthedocs.org/projects/pymongo/builds/

13. Bump the version number to <next version>.dev0 in setup.py/__init__.py,
12. Bump the version number to <next version>.dev0 in setup.py/__init__.py,
commit, push.

14. Publish the release version in Jira.
13. Publish the release version in Jira.

15. Announce the release on:
14. Announce the release on:
https://developer.mongodb.com/community/forums/c/community/release-notes/

16. File a ticket for DOCSP highlighting changes in server version and Python
15. File a ticket for DOCSP highlighting changes in server version and Python
version compatibility or the lack thereof, for example:
https://jira.mongodb.org/browse/DOCSP-13536