Skip to content

Commit e140027

Browse files
committed
Move checklist to issue template
1 parent e6ff423 commit e140027

File tree

1 file changed

+2
-21
lines changed

1 file changed

+2
-21
lines changed

RELEASING.md

Lines changed: 2 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -7,27 +7,8 @@ information about how the version numbers line up with releases.
77

88
Released quarterly on January 2nd, April 1st, July 1st and October 15th.
99

10-
* [ ] Open a release ticket e.g. https://github.com/python-pillow/Pillow/issues/3154
11-
* [ ] Develop and prepare release in `main` branch.
12-
* [ ] Check [GitHub Actions](https://github.com/python-pillow/Pillow/actions) to confirm passing tests in `main` branch.
13-
* [ ] Check that all the wheel builds pass the tests in the [GitHub Actions "Wheels" workflow](https://github.com/python-pillow/Pillow/actions/workflows/wheels.yml) jobs by manually triggering them.
14-
* [ ] In compliance with [PEP 440](https://peps.python.org/pep-0440/), update version identifier in `src/PIL/_version.py`
15-
* [ ] Run pre-release check via `make release-test` in a freshly cloned repo.
16-
* [ ] Create branch and tag for release e.g.:
17-
```bash
18-
git branch 5.2.x
19-
git tag 5.2.0
20-
git push --tags
21-
```
22-
* [ ] Check the [GitHub Actions "Wheels" workflow](https://github.com/python-pillow/Pillow/actions/workflows/wheels.yml)
23-
has passed, including the "Upload release to PyPI" job. This will have been triggered
24-
by the new tag.
25-
* [ ] Publish the [release on GitHub](https://github.com/python-pillow/Pillow/releases).
26-
* [ ] In compliance with [PEP 440](https://peps.python.org/pep-0440/),
27-
increment and append `.dev0` to version identifier in `src/PIL/_version.py` and then:
28-
```bash
29-
git push --all
30-
```
10+
* [ ] Create a new issue and select the "Release" template.
11+
3112
## Point Release
3213

3314
Released as needed for security, installation or critical bug fixes.

0 commit comments

Comments
 (0)