Version 0.17.1

[LarsStegman]

Changes: 0.17.0..master
GitHub Draft release: here

[Kludex]

Next steps:

• @tomchristie needs to give you maintainer status,
• Create the draft release.
• Get this approved.
• Create tag 0.17.1 and push it
• Draft -> Release

[tomchristie]

Invite sent.

As @Kludex says, once you're a maintainer, head over to the releases section, and create a new draft release...

Make sure to hit the "save draft" button not the "publish release".

And pop back to this thread so we can approve it.

Aside: It'd kinda be nice from my POV if GH had some more control over this process. Still find it a bit easy too easy get it unintentionally wrong.

I suppose we could alternately consider doing this process the other way around, and merging a release PR before we author the release stuff?

[LarsStegman]

I have created the draft release

[tomchristie]

@LarsStegman - Fab...

• Merge this PR.
• Publish the release.
• Check that the publish action runs okay, and that the new release ends up on PyPI.

[tomchristie]

Hey presto! 🌟

It's not too bad our release process, eh? I'm sure we've got a few little improvements we could make to on boarding folks into maintainer-ship, and it'd be nice if this process had a few more guardrails perhaps, but pretty neat really, thanks to PyPI tokens & GitHub's actions support.

[LarsStegman]

Yeah, it's quite an easy process. It's nice there is no hassle to get the version deployed to PyPI.