Deployed 7e7de6f with MkDocs version: 1.6.1

community/project-management/index.html

@@ -2852,45 +2852,43 @@ <h4 id="responsibilities">Responsibilities<a class="headerlink" href="#responsib
 <hr />
 <h2 id="release-process">Release process<a class="headerlink" href="#release-process" title="Permanent link">&para;</a></h2>
 <ul>
-<li>The release manager is selected by <code>@tomchristie</code>.</li>
+<li>The release manager is selected.</li>
 <li>The release manager will then have the maintainer role added to PyPI package.</li>
 <li>The previous manager will then have the maintainer role removed from the PyPI package.</li>
 </ul>
-<p>Our PyPI releases will be handled by either the current release manager, or by <code>@tomchristie</code>. Every release should have an open issue tagged with the <code>Release</code> label and marked against the appropriate milestone.</p>
-<p>The following template should be used for the description of the issue, and serves as a release checklist.</p>
-<div class="language-text highlight"><pre><span></span><code>Release manager is @***.
-Pull request is #***.
-
-Checklist:
-
-- [ ] Create pull request for [release notes](https://github.com/encode/django-rest-framework/blob/mains/docs/topics/release-notes.md):
-    - Start drafting a new release in GitHub: https://github.com/encode/django-rest-framework/releases/new
-    - Select the tag that you want to give to the next release and the previous tag
-    - Click the &quot;Generate release notes&quot; button
-    - Don&#39;t confirm anything yet! Copy the generated content to a file `input.md`
-    - Run `uv tool run linkify-gh-markdown input.md` to make the links absolute
-    - Put the generated content in the release-notes.md file
-- [ ] Update supported versions:
-    - [ ] `pyproject.toml` `python_requires` list
-    - [ ] `pyproject.toml` Python &amp; Django version trove classifiers
-    - [ ] `README` Python &amp; Django versions
-    - [ ] `docs` Python &amp; Django versions
-- [ ] Ensure the pull request increments the version to `*.*.*` in [`restframework/__init__.py`](https://github.com/encode/django-rest-framework/blob/main/rest_framework/__init__.py).
-- [ ] Ensure documentation validates
-    - Build and serve docs `mkdocs serve`
-    - Validate links `pylinkvalidate.py -P http://127.0.0.1:8000`
-- [ ] Confirm with other maintainers that the release is finalized and ready to go.
-- [ ] Ensure that release date is included in pull request.
-- [ ] Merge the release pull request.
-- [ ] Tag the release, either with `git tag -a *.*.* -m &#39;version *.*.*&#39;; git push --tags` or in GitHub.
-- [ ] Wait for the release workflow to run. It will build the distribution, upload it to Test PyPI, PyPI and create the GitHub release.
-- [ ] Make a release announcement on the [discussion group](https://groups.google.com/forum/?fromgroups#!forum/django-rest-framework).
-- [ ] Make a release announcement on social media (Mastodon, etc...) and on the [Django forum](https://forum.djangoproject.com/).
-- [ ] Close the milestone on GitHub.
-
-To modify this process for future releases make a pull request to the [project management](https://www.django-rest-framework.org/topics/project-management/) documentation.
-</code></pre></div>
-<p>When pushing the release to PyPI ensure that your environment has been installed from our development <code>requirement.txt</code>, so that documentation and PyPI installs are consistently being built against a pinned set of packages.</p>
+<p>Our PyPI releases is automated in GitHub actions on tag pushes. The following template can be used as a release checklist:</p>
+<ul>
+<li>Create pull request for <a href="https://github.com/encode/django-rest-framework/blob/mains/docs/topics/release-notes.md">release notes</a>:<ul>
+<li>Start drafting a <a href="https://github.com/encode/django-rest-framework/releases/new">new release in GitHub</a></li>
+<li>Select the tag that you want to give to the release and the previous tag</li>
+<li>Click the "Generate release notes" button</li>
+<li>Don't confirm anything! Copy the generated content to a file <code>input.md</code></li>
+<li>Run <code>uv tool run linkify-gh-markdown input.md</code> to make the links absolute</li>
+<li>Put the generated content in the <code>release-notes.md</code> file</li>
+</ul>
+</li>
+<li>Update supported versions:<ul>
+<li><code>pyproject.toml</code> <code>python_requires</code> list</li>
+<li><code>pyproject.toml</code> Python &amp; Django version trove classifiers</li>
+<li><code>README</code> Python &amp; Django versions</li>
+<li><code>docs</code> Python &amp; Django versions</li>
+</ul>
+</li>
+<li>Ensure the pull request increments the version to <code>*.*.*</code> in <a href="https://github.com/encode/django-rest-framework/blob/main/rest_framework/__init__.py"><code>restframework/__init__.py</code></a>.</li>
+<li>Ensure documentation validates<ul>
+<li>Build and serve docs <code>mkdocs serve</code></li>
+<li>Validate links <code>pylinkvalidate.py -P http://127.0.0.1:8000</code></li>
+</ul>
+</li>
+<li>Confirm with other maintainers that the release is finalized and ready to go.</li>
+<li>Ensure that release date is included in pull request.</li>
+<li>Merge the release pull request.</li>
+<li>Tag the release, either with <code>git tag -a *.*.* -m 'version *.*.*'; git push --tags</code> or in GitHub.</li>
+<li>Wait for the release workflow to run. It will build the distribution, upload it to Test PyPI, PyPI and create the GitHub release.</li>
+<li>Make a release announcement on the <a href="https://groups.google.com/forum/?fromgroups#!forum/django-rest-framework">discussion group</a>.</li>
+<li>Make a release announcement on social media (Mastodon, etc...) and on the <a href="https://forum.djangoproject.com/">Django forum</a>.</li>
+<li>Close the milestone on GitHub.</li>
+</ul>
 <hr />
 <h2 id="project-ownership">Project ownership<a class="headerlink" href="#project-ownership" title="Permanent link">&para;</a></h2>
 <p>The PyPI package is owned by <code>@tomchristie</code>. As a backup <code>@j4mie</code> also has ownership of the package.</p>