sklam · Jun 15, 2021 · Apr 30, 2021 · May 3, 2021 · May 21, 2021 · May 21, 2021
diff --git a/.github/ISSUE_TEMPLATE/first_rc_checklist.md b/.github/ISSUE_TEMPLATE/first_rc_checklist.md
@@ -0,0 +1,38 @@
+---
+name: First Release Candidate Checklist (maintainer only)
+about: Checklist template for the first release of every series
+title: Numba X.Y.Zrc1 Checklist (FIXME)
+labels: task
+
+---
+
+
+## Numba X.Y.Z
+
+* [ ] Merge to master.
+    - [ ] "remaining Pull-Requests from milestone".
+* [ ] Merge change log changes.
+    - [ ] "PR with changelog entries".
+* [ ] Create X.Y release branch.
+* [ ] Pin llvmlite to `>=0.A.0rc1,<0.A+1.0`.
+* [ ] Annotated tag X.Y.Zrc1 on release branch.
+* [ ] Build and upload conda packages on buildfarm (check "upload").
+* [ ] Build wheels (`$PYTHON_VERSIONS`) on the buildfarm.
+* [ ] Upload wheels and sdist to PyPI (upload from `ci_artifacts`).
+* [ ] Verify packages uploaded to Anaconda Cloud and move to
+  `numba/label/main`.
+* [ ] Verify wheels for all platforms arrived on PyPi.
+* [ ] Verify ReadTheDocs build.
+* [ ] Clean up `ci_artifacts`.
+* [ ] Review, merge and check execution of release notebook.
+* [ ] Send RC announcement email / post announcement to discourse group.
+* [ ] Post link to Twitter.
+* [ ] Post link to python-announce-list@python.org.
+
+### Post Release:
+
+* [ ] Tag X.Y+1.0dev0 to start new development cycle on `master`.
+* [ ] Update llvmlite dependency spec to match next version via PR to `master`.
+* [ ] Update release checklist template with any additional bullet points that
+      may have arisen during the release.
+* [ ] Close milestone (and then close this release issue).
diff --git a/.github/ISSUE_TEMPLATE/sub_rc_checklist.md b/.github/ISSUE_TEMPLATE/sub_rc_checklist.md
@@ -0,0 +1,33 @@
+---
+name: Subsequent Release Candidate Checklist (maintainer only)
+about: Checklist template for all subsequent releases (RC 2-N, FINAL and PATCH) of every series
+title: Numba X.Y.Zrc1 Checklist (FIXME)
+labels: task
+
+---
+
+
+## numba X.Y.Z
+
+* [ ] Cherry-pick items from the X.Y.Z milestone into a PR.
+* [ ] Merge change log modifications and cherry-picks to X.Y release branch.
+  * [ ] https://github.com/numba/numba/pull/XXXX
+* [ ] Annotated tag X.Y.Z on release branch (no `v` prefix).
+* [ ] Build and upload conda packages on buildfarm (check "upload").
+* [ ] Build wheels (`$PYTHON_VERSIONS`) on the buildfarm.
+* [ ] Upload wheels and sdist to PyPI (upload from `ci_artifacts`).
+* [ ] Verify packages uploaded to Anaconda Cloud and move to
+  `numba/label/main`.
+* [ ] Verify wheels for all platforms arrived on PyPi.
+* [ ] Verify ReadTheDocs build.
+* [ ] Clean up `ci_artifacts`.
+* [ ] Send RC/FINAL announcement email / post announcement to discourse group.
+* [ ] Post link to Twitter.
+* [ ] Post link to python-announce-list@python.org.
+
+### Post release
+
+* [ ] Cherry-pick change-log modifications to main branch (`master`) via PR.
+* [ ] Update release checklist template.
+* [ ] Ping Anaconda Distro team to trigger a build for `defaults` (FINAL ONLY).
+* [ ] Close milestone (and then close this release issue).
diff --git a/docs/source/developer/index.rst b/docs/source/developer/index.rst
@@ -8,6 +8,7 @@ Developer Manual
    :maxdepth: 2
 
    contributing.rst
+   release.rst
    repomap.rst
    architecture.rst
    dispatching.rst

diff --git a/docs/source/developer/release.rst b/docs/source/developer/release.rst
@@ -0,0 +1,49 @@
+Numba Release Process
+=====================
+
+The goal of the Numba release process -- from a high level perspective -- is to
+publish source and binary artifacts that correspond to a given version
+number. This usually involves a sequence of individual tasks that must be
+performed in the correct order and with diligence. Numba and llvmlite are
+commonly released in lockstep since there is usually a one-to-one mapping
+between a Numba version and a corresponding llvmlite version.
+
+This section contains various notes and templates that can be used to create a
+Numba release checklist on the Numba Github issue tracker. This is an aid for
+the maintainers during the release process and helps to ensure that all tasks
+are completed in the correct order and that no tasks are accidentally omitted.
+
+If new or additional items do appear during release, please do remember to add
+them to the checklist templates. Also note that the release process itself is
+always a work in progress. This means that some of the information here may be
+outdated. If you notice this please do remember to submit a pull-request to
+update this document.
+
+All release checklists are available as Gitub issue templates. To create a new
+release checklist simply open a new issue and select the correct template.
+
+
+Primary Release Candidate Checklist
+-----------------------------------
+
+This is for the first/primary release candidate for minor release i.e. the
+first release of every series. It is special, because during this release, the
+release branch will have to be created. Release candidate indexing begins at 1.
+
+.. literalinclude:: ../../../.github/ISSUE_TEMPLATE/first_rc_checklist.md
+    :language: md
+    :lines: 9-
+
+`Open a primary release checklist <https://github.com/numba/numba/issues/new?template=first_rc_checklist.md>`_.
+
+Subsequent Release Candidates, Final Releases and Patch Releases
+----------------------------------------------------------------
+
+Releases subsequent to the first release in a series usually involves a series
+of cherry-picks, the recipe is therefore slightly different.
+
+.. literalinclude:: ../../../.github/ISSUE_TEMPLATE/sub_rc_checklist.md
+    :language: md
+    :lines: 9-
+
+`Open a subsequent release checklist <https://github.com/numba/numba/issues/new?template=sub_rc_checklist.md>`_.