I'll likely do the release today around 5PM pacific.

https://ipython.readthedocs.io/en/latest/coredev/#ipython-release-process

Thanks Wes, this is already linked in my first point.

• release issue and PR templates in /.github/ISSUE_TEMPLATE/release.md and/or /.github/PULL_REQUEST_TEMPLATE/release.md?

See: https://github.com/devspace/awesome-github-templates

• 7.1 -- October 27, 2018 (according to https://github.com/ipython/ipython/releases )
• 7.2 -- November 29, 2018

Do we wait a few days for bugs to shake out before updating the conda feedstock?
Does conda have a prerelease capability like pip install --pre?

• Notify downstream packagers (OS packages: RPM, DEB)
  • it may be worth sending the release announcement to downstream package maintainers' emails
    • create list of people to notify of new releases

... It's now possible to watch a gh repo and get notifications only for releases

Update conda forge feedstock

i'm your huckleberry. or rather, the bot will be. I'll take a crack packaging at master right now locally and see if we are in for any surprises.

Does conda have a prerelease capability like pip install --pre?

Conda does, (labels, which are really just more channels) but conda-forge doesn't have a good process in place to do it, yet.

• release issue and PR templates in

For release ? I don't think it's really worth it.

Do we wait a few days for bugs to shake out before updating the conda feedstock?

I don't think its really worth it. Most of our install are via conda, so it's better to widely spread the release. Anyway if there is a bug, I'm not going to make another 7.2 release I'm going to do a 7.2.1 or a 7.3 so the result is the same.

Notify downstream packagers

So far I haven't got any interest of downstream maintainer to be pinged on releases.

Release process started.
Commit and tag should be on github now.

commit 523ed2f (tag: 7.2.0)

$ shasum -a 256 dist/*
f69932b1e806b38a7818d9a1e918e5821b685715040b48e59c657b3c7961b742  dist/ipython-7.2.0-py3-none-any.whl
6a9496209b76463f1dec126ab928919aaf1f55b38beb9219af3fe202f6bbdd12  dist/ipython-7.2.0.tar.gz

Here are (will be) the sha256 of the wheel and sdist.

Good, IPython 7.2 is out ! I've done almost everything that requires a core dev.
If anyone is interesting in tackling the remaining points I'm happy not to do it.

I've updated a couple of tasks in the top comment.

Cool, just waiting for ⚪ 🐧

ipython/ipython-website#143 should be ready to merge.

There's really a lot of duplication here; there's likely opportunity for a tool to handle structured data:

• Release version (*)
• Release date (*)
• Release short desc (ipython-website/index.rst, ipython-website/news.rst, whatsnew first paragraph, release tweet)
• Release full desc with PR references (whatsnew, ml release announcement)

CPython discussed tools for release logs and decided on blurb. (Notes re: a more useful, IMHO, linked data approach: python/core-workflow#6 (comment)). A task for a different day, I suppose.

• release issue and PR templates in

For release ? I don't think it's really worth it.

Instead of release manager(s) copy-pasting this issue description for every release, I think a release issue template would take a worthwhile 5 minutes.

• Help Welcomed: Update the ipython website (ipython/ipython-website), see for example ipython/ipython-website@9c021b5 and do the same to annouce the release and release date of 7.1 and 7.2

ipython/ipython-website#143 is ready to merge.

• Help Welcomed: Update the wikipedia page to point to latest release and its date.

Done. https://en.wikipedia.org/wiki/IPython

Many thanks to you @westurner.

I've done the announce on discourse (https://discourse.jupyter.org/t/release-of-ipython-7-2/226)

All done. closing.

"Release 7.3" #11571

Thanks !