Skip to content

Commit dea2ace

Browse files
committed
Add release process for DBX team members
1 parent 0485572 commit dea2ace

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

docs/internals/release-process.rst

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,3 +40,25 @@ merge of a "Add support for Django X.Y" pull request. Before merging that pull
4040
request, a branch is created off of main to track the previous feature release.
4141
For example, the 5.1.x branch is created shortly after the release of Django
4242
5.2, and main starts tracking the Django 5.2.x series.
43+
44+
Release
45+
=======
46+
47+
Django MongoDB Backend uses GitHub Actions to publish new releases to PyPI. To
48+
publish a new release to PyPI:
49+
50+
- Bump the version number in ``django_mongodb_backend/__init__.py``
51+
according to :ref:`the supported versions policy
52+
<supported-versions-policy>`.
53+
54+
- Update the release notes in ``docs/releases/#.#.x.rst`` for the new version.
55+
56+
- Run the ``Release`` workflow on GitHub Actions, providing the new (dev)
57+
version number as input.
58+
59+
- First run with ``Dry Run?`` selected and check test PyPI to ensure that
60+
`pip install` works as expected.
61+
62+
- Then run without ``Dry Run?`` to publish the release to PyPI.
63+
64+
- Announce the new release on the relevant communication channels.

0 commit comments

Comments
 (0)