python-pillow/Pillow
1
1
Fork 0
mirror of https://github.com/python-pillow/Pillow.git synced 2025-07-27 08:30:05 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Release Checklist (markdown)

wiredfool 2014-09-05 09:29:31 -07:00
parent 1f94e19ffc
commit 342933463d
1 changed files with 58 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

114
Release-Checklist.md → Release Checklist.md

@ -1,56 +1,58 @@
# Release checklist
In [#853](https://github.com/python-pillow/Pillow/issues/853#issuecomment-52655451) @wiredfool said a release checklist is needed. Here's a rough draft to be filled in. It can be moved from the wiki to the master repo if that's better.
## Main release
Released Quarterly.
* [ ] Get master to the appropriate code release state. Travis should be running cleanly for all merges to master.
* [ ] Update version in `PIL/__init__.py`, `setup.py`, `_imaging.c`, Update date in `CHANGES.rst`
* [ ] Tag and push to release branch in python-pillow repo.
* [ ] Upload Binaries
## Point Release
Released as required for security or installation fixes.
* [ ] Make necessary changes in master
* [ ] Cherry pick individual commits. Touch up `CHANGES.rst` to reflect reality.
* [ ] Update version in `PIL/__init__.py`, `setup.py`, `_imaging.c`
* [ ] Push to release branch in personal repo. Let Travis run cleanly.
* [ ] Tag and push to release branch in python-pillow repo.
* [ ] Upload Binaries
## Embargoed Release
Security fixes that need to be pushed to the distros prior to public release.
* [ ] Prepare patch for all versions that will get a fix. Test against local installations.
* [ ] Commit against master, cherry pick to affected release branches.
* [ ] Run local test matrix on each release & python version.
* [ ] Privately send to distros.
* [ ] Amend any commits with the CVE #
* [ ] On release date, tag and push to GitHub.
```
git checkout 2.5.x
git tag 2.5.3
git push origin 2.5.x
git push origin --tags
```
* [ ] Upload Binaries
## Binary Upload Process
* [ ] Ping cgohlke for windows binaries
* [ ] From a clean source directory with no extra temp files:
```
python setup.py register
python setup.py sdist --format=zip upload
```
* [ ] Push a commit to https://github.com/python-pillow/pillow-wheels to build OSX versions (UNDONE latest tag or specific release???)
* [ ] Retrieve the OSX Wheels from Rackspace files, upload to pypy (twine?)
* [ ] Grab windows binaries, `twine upload dist/*.[whl|egg]`. Manually upload .exe installers.
* [ ] Announce release availability. Twitter, web.
# Release checklist
In [#853](https://github.com/python-pillow/Pillow/issues/853#issuecomment-52655451) @wiredfool said a release checklist is needed. Here's a rough draft to be filled in. It can be moved from the wiki to the master repo if that's better.
## Main release
Released Quarterly.
* [ ] Get master to the appropriate code release state. Travis should be running cleanly for all merges to master.
* [ ] Update version in `PIL/__init__.py`, `setup.py`, `_imaging.c`, Update date in `CHANGES.rst`
* [ ] Tag and push to release branch in python-pillow repo.
* [ ] Upload Binaries
## Point Release
Released as required for security or installation fixes.
* [ ] Make necessary changes in master
* [ ] Cherry pick individual commits. Touch up `CHANGES.rst` to reflect reality.
* [ ] Update version in `PIL/__init__.py`, `setup.py`, `_imaging.c`
* [ ] Push to release branch in personal repo. Let Travis run cleanly.
* [ ] Tag and push to release branch in python-pillow repo.
* [ ] Upload Binaries
## Embargoed Release
Security fixes that need to be pushed to the distros prior to public release.
* [ ] Prepare patch for all versions that will get a fix. Test against local installations.
* [ ] Commit against master, cherry pick to affected release branches.
* [ ] Run local test matrix on each release & python version.
* [ ] Privately send to distros.
* [ ] Amend any commits with the CVE #
* [ ] On release date, tag and push to GitHub.
```
git checkout 2.5.x
git tag 2.5.3
git push origin 2.5.x
git push origin --tags
```
* [ ] Upload Binaries
## Binary Upload Process
* [ ] Ping cgohlke for windows binaries
* [ ] From a clean source directory with no extra temp files:
```
python setup.py register
python setup.py sdist --format=zip upload
python setup.py sdist upload
```
(Debian requests a tarball, everyone else would just prefer that we choose one and stick to it. So both it is)
* [ ] Push a commit to https://github.com/python-pillow/pillow-wheels to build OSX versions (UNDONE latest tag or specific release???)
* [ ] Retrieve the OSX Wheels from Rackspace files, upload to pypy (twine?)
* [ ] Grab windows binaries, `twine upload dist/*.[whl|egg]`. Manually upload .exe installers.
* [ ] Announce release availability. Twitter, web.