@@ -43,18 +43,15 @@ Doing a Release
43
43
3. Add release notes to doc/changelog.rst. Generally just summarize/clarify
44
44
the git log, but you might add some more long form notes for big changes.
45
45
46
- 4. Search and replace the "devN" version number w/ the new version number (see
47
- note above in `Versioning `_).
46
+ 4. Make sure version number is updated in ``pymongo/_version.py ``
48
47
49
- 5. Make sure version number is updated in setup.py and pymongo/__init__.py
48
+ 5. Commit with a BUMP version_number message, eg `` git commit -m 'BUMP 3.11.0' ``.
50
49
51
- 6. Commit with a BUMP version_number message , eg ``git commit - m 'BUMP 3.11.0' ``.
50
+ 6. Tag w/ version_number, eg, ``git tag -a '3.11.0' - m 'BUMP 3.11.0' <COMMIT> ``.
52
51
53
- 7. Tag w/ version_number , eg, ``git tag -a '3.11.0' -m '3.11.0' <COMMIT> ``.
52
+ 7. Push commit / tag , eg ``git push && git push --tags ``.
54
53
55
- 8. Push commit / tag, eg ``git push && git push --tags ``.
56
-
57
- 9. Pushing a tag will trigger a release process in Evergreen which builds
54
+ 8. Pushing a tag will trigger a release process in Evergreen which builds
58
55
wheels for manylinux, macOS, and Windows. Wait for the "release-combine"
59
56
task to complete and then download the "Release files all" archive. See:
60
57
https://evergreen.mongodb.com/waterfall/mongo-python-driver?bv_filter=release
@@ -70,27 +67,27 @@ Doing a Release
70
67
...
71
68
pymongo-<version>.tar.gz
72
69
73
- 10 . Upload all the release packages to PyPI with twine::
70
+ 9 . Upload all the release packages to PyPI with twine::
74
71
75
72
$ python3 -m twine upload path/to/archive/*
76
73
77
- 11 . Make sure the new version appears on https://pymongo.readthedocs.io/. If the
74
+ 10 . Make sure the new version appears on https://pymongo.readthedocs.io/. If the
78
75
new version does not show up automatically, trigger a rebuild of "latest":
79
76
https://readthedocs.org/projects/pymongo/builds/
80
77
81
- 12 . Bump the version number to <next version>.dev0 in setup.py/__init__ .py,
78
+ 11 . Bump the version number to <next version>.dev0 in `` pymongo/_version .py`` ,
82
79
commit, push.
83
80
84
- 13 . Publish the release version in Jira.
81
+ 12 . Publish the release version in Jira.
85
82
86
- 14 . Announce the release on:
83
+ 13 . Announce the release on:
87
84
https://www.mongodb.com/community/forums/c/announcements/driver-releases/110
88
85
89
- 15 . File a ticket for DOCSP highlighting changes in server version and Python
86
+ 14 . File a ticket for DOCSP highlighting changes in server version and Python
90
87
version compatibility or the lack thereof, for example:
91
88
https://jira.mongodb.org/browse/DOCSP-13536
92
89
93
- 16 . Create a GitHub Release for the tag using
90
+ 15 . Create a GitHub Release for the tag using
94
91
https://github.com/mongodb/mongo-python-driver/releases/new.
95
92
The title should be "PyMongo X.Y.Z", and the description should contain
96
93
a link to the release notes on the the community forum, e.g.
0 commit comments